Malicious code in fca-raihan (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (241006adda5ea773d76d48d874c80a4054215ed18f05de3e392cdd86c0379785) package.json for fca-raihan declares a dependency whose key equals the package's own name (`fca-raihan`) with source `github:raihan9099/fca-raihan`. This is an off-registry dependency source with no ref pin and no integrity check: on `npm install`, npm fetches the current HEAD of that GitHub repository and installs whatever tree it returns, running any lifecycle scripts contained in the fetched code. Whoever controls the repository can change what gets installed at any time, independently of what is published to the npm registry, and the self-named dependency-confusion shape (dependency key equal to the package's own name) causes this source to be resolved during normal installs of fca-raihan. Additional patterns observed in the shipped source include Buffer.from(..., 'base64') decoding in messaging/e2ee modules and `ping` string occurrences in a bundled Facebook e2ee vendor file; these are consistent with the package's advertised messaging/E2EE functionality and are not by themselves indicative of installer harm, but they are not analyzable independently of whatever the mutable GitHub source resolves to at install time.

Source published

30 Sep 2026 04:51:09 UTC

Source modified

30 Sep 2026 05:30:05 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.