Which versions of stat-fns are malicious?

The following npm versions of stat-fns are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate stat-fns if I installed it?

stat-fns 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 stat-fns — how do I know if it already compromised me?

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

Yes — stat-fns is associated with the GHSA-fcvh-m28w-5rw9 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 stat-fns 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 stat-fns (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stat-fns across your stack and pipelines.

Malicious package

stat-fnsnpm

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

MAL-2025-191013

Immediate action

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

npm uninstall stat-fns

What this malware does

The package stat-fns 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6c2e197e85b015babcf3a2073e3f76b980a3ae924a49a20d9c1648c610d7d3c0

f5395e07a1f1a743d77d42495c7eaf08cb0ced22a0b0883b53b5adf78beef28a

435518e57f26cdd1c509283e989e909f13edc1338e36d9857ef8c968437e74d2

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 stat-fns (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stat-fns across your stack and pipelines.
If you installed it — respond
stat-fns 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 stat-fns 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 stat-fns 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. stat-fns on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fcvh-m28w-5rw9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks stat-fns-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