Which versions of shadowx-fca are malicious?

The following npm versions of shadowx-fca are flagged malicious: 10.0.0, 10.1.0. Treat any of these as compromised.

How do I remediate shadowx-fca if I installed it?

shadowx-fca is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed shadowx-fca — how do I know if it already compromised me?

If shadowx-fca 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.

Is shadowx-fca part of a known attack campaign?

Yes — shadowx-fca is associated with the IN-MAL-2026-016818, IN-MAL-2026-016819 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find shadowx-fca across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shadowx-fca (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shadowx-fca across your stack and pipelines.

Malicious package

shadowx-fcanpm

shadowx-fca is a confirmed malicious npm package (MAL-2026-13457) that steals credentials and exfiltrates sensitive data (malicious versions 10.0.0, 10.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shadowx-fca (npm)

MAL-2026-13457

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall shadowx-fca

What this malware does

The package advertises a Facebook Chat API (FCA) client. Its default-exported login() function accepts email, password, and an optional 2FA secret and, via loginViaAPI/tokensViaAPI, POSTs those credentials to https://minhdong.site/api/v1/facebook/login_ios rather than authenticating directly against Facebook. The destination is set as the default apiServer in module/config.js (defaultConfig.apiServer = "https://minhdong.site") and loadConfig executes at import time from module/login.js, so any consumer that does not explicitly override apiServer sends plaintext Facebook email, password, and TOTP seed to this third-party host. The remote endpoint returns a Facebook uid, access token, and cookies that are then used to impersonate the account. The domain minhdong.site is unrelated to Facebook and to the declared npm publisher.

Malicious versions

2 flagged

10.0.010.1.0

Indicators of compromise (SHA-256)

5e05ec19966fd3fff65969ab898a3b25da7e1fa0baf271ee9b75dadad8513c27

8973ae32a1add1000f7914e9a86c0af54d24e70f3cf5610c3dcdf547bc20d76c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shadowx-fca (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shadowx-fca across your stack and pipelines.
If you installed it — respond
shadowx-fca is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If shadowx-fca 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 shadowx-fca 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

No. shadowx-fca on npm has been identified as a malicious package (versions 10.0.0, 10.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016818IN-MAL-2026-016819

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shadowx-fca-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database