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

elf-stats-cosy-sleigh-356npm

Malicious code in elf-stats-cosy-sleigh-356 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191980
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall elf-stats-cosy-sleigh-356

What this malware does

The package elf-stats-cosy-sleigh-356 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-cosy-sleigh-356' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
99.0.099.0.1

Indicators of compromise (SHA-256)

43e46a0bed35ce4be86328e6015014bb6db224d38e70ab466202c79bad015323
2d68bf61b3458f8965a4a4fb7d30007c37aaddd4a98ef70d354064df191e587e
652541110042747785243bf4be3068d0ceb8e65bfcf674ed6e2f74f5ebf10678
f54ec7bffb7555b959d9a7dbb5abf06b4ffa4a8e9c32dac20f579b6725896f1d

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-cosy-sleigh-356 (2 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-cosy-sleigh-356 across your stack and pipelines.

  2. If you installed it — respond

    Remove elf-stats-cosy-sleigh-356 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-cosy-sleigh-356 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-cosy-sleigh-356 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-cosy-sleigh-356 on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m24m-gvqg-6m35RLMA-2025-06161

References

Credits

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

Detect & block this

O3 blocks elf-stats-cosy-sleigh-356-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-cosy-sleigh-356 (npm) malicious package — MAL-2025-191980 | O3 Security