Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

elf-stats-fuzzy-fir-973npm

Malicious code in elf-stats-fuzzy-fir-973 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191973
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall elf-stats-fuzzy-fir-973

What this malware does

The package elf-stats-fuzzy-fir-973 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.

The OpenSSF Package Analysis project identified 'elf-stats-fuzzy-fir-973' @ 1.0.3 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged
1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

15f70e8313817f9705f9e5799d1f9d23284338d0821f03d9730e4eeb41c30a0c
215a95aefa023baa8138a02bd7d68bbdd09b9f0bdff4595f45cdd42a2997255e
0ba9ac3d769ab2aba246c55a722520c8b05ef3c7002ccd71877535caf29b7403
d7169170d7ef0abba045a713ae2e2bd66b93b08089de3cd0d13b842740fde537

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove elf-stats-fuzzy-fir-973 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.

  3. Did it already run?

    If elf-stats-fuzzy-fir-973 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.

  4. How O3 protects you

    O3 blocks elf-stats-fuzzy-fir-973 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. elf-stats-fuzzy-fir-973 on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-868x-5vrm-qv2mRLMA-2025-06193

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks elf-stats-fuzzy-fir-973-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.

elf-stats-fuzzy-fir-973 (npm) malicious package — MAL-2025-191973 | O3 Security