Which versions of cyber-fca are malicious?

The following npm versions of cyber-fca are flagged malicious: 1.0.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4. Treat any of these as compromised.

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

Remove cyber-fca 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.

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

If cyber-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 cyber-fca part of a known attack campaign?

Yes — cyber-fca is associated with the GHSA-fwq7-wx79-2667 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 cyber-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 cyber-fca (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cyber-fca across your stack and pipelines.

Malicious package

cyber-fcanpm

Malicious code in cyber-fca (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191537

Immediate action

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

npm uninstall cyber-fca

What this malware does

The package cyber-fca was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

6 flagged

1.0.02.0.02.0.12.0.22.0.32.0.4

Indicators of compromise (SHA-256)

c7c387785610633bef06443bfd2ecd4a274d3d1265e22822b04579fae216ba2c

b577f3dcb8f7ebe36e69f65a8b605a23ff2dbdb7d896e78bc20f1880331a238c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cyber-fca (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cyber-fca across your stack and pipelines.
If you installed it — respond
Remove cyber-fca 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 cyber-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 cyber-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. cyber-fca on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fwq7-wx79-2667

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cyber-fca-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.

Malware detection Runtime egress monitoring