NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@eryxenx/fcanpm

Advisory published Updated

@eryxenx/fca is a confirmed malicious npm package (MAL-2026-20276) that steals credentials and exfiltrates sensitive data (malicious versions 1.3.0, 1.3.1, 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @eryxenx/fca (npm)

MAL-2026-20276
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @eryxenx/fca

What this malware does

The package is published as a Facebook Chat API client but its login flow (loginViaAPI in module/loginHelper.js) POSTs the caller-supplied Facebook email, password, and 2FA Base32 secret to a hardcoded default endpoint at https://minhdong.site/api/v1/facebook/login_ios. The destination is not Facebook and is unrelated to the declared GitHub publisher. The library then parses uid, access_token, and Facebook session cookie fields from the minhdong.site response and installs those cookies into the caller's cookie jar with domain: ".facebook.com" as the live Facebook session. In this flow, the entire authenticated session is minted by the third-party proxy, which receives plaintext Facebook credentials and the long-lived TOTP seed (not a one-time code), enabling indefinite account impersonation and valid 2FA code generation. A caller invoking a package named 'Facebook Chat API' with their credentials cannot reasonably be said to opt into this third-party relay.

Malicious versions

3 flagged
1.3.01.3.11.3.2

Indicators of compromise (SHA-256)

be87e23a68dcaa5fda94bc33643c3e211dca191bbc5a4168a8f6560d9f0fd84f
cc19a43b746ed0a24a12abb487b2b16e8fbf3340605c9764f53a43dedffbd082
dc1565a3c533cd9f801edea2505efe5a04f5da569e3be9ef33b4e1271e7a5266

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @eryxenx/fca (3 malicious versions).

  2. If you installed it — respond

    @eryxenx/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.

  3. Did it already run?

    If @eryxenx/fca was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @eryxenx/fca on npm has been identified as a malicious package (versions 1.3.0, 1.3.1, 1.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022913IN-MAL-2026-022911IN-MAL-2026-022912

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @eryxenx/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.

Explore

@eryxenx/fca (npm) malicious package — MAL-2026-20276 | O3 Security