Malicious code in fca-raihan (npm)
--- _-= 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.
Malicious code in fca-raihan (npm)
Description
--- _-= 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17328
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abcdddd0df196e1a9da6f5d
Added to database: 09/30/2026, 10:01:01 UTC
Last updated: 09/30/2026, 10:01:01 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.