fca-raihannpm
fca-raihan is a confirmed malicious npm package (MAL-2026-17328) that executes malicious code on install (malicious versions 37.2.5, 37.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fca-raihan (npm)
What this malware does
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 versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fca-raihan (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fca-raihan across your stack and pipelines.
If you installed it — respond
Remove fca-raihan from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If fca-raihan was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks fca-raihan before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks fca-raihan-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.