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

elf-stats-ginger-hammer-326npm

Malicious code in elf-stats-ginger-hammer-326 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191982
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall elf-stats-ginger-hammer-326

What this malware does

The package elf-stats-ginger-hammer-326 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'elf-stats-ginger-hammer-326' @ 1.0.3 (npm) as malicious.

It is considered malicious because:

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

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.0.31.0.42.0.1

Indicators of compromise (SHA-256)

ab28db009d546523ca9bfce3468ed5b176df45db15f988ba15d36c0d6a6e7151
b381aa5a37f1282740de384eeff72f5f4d3e57918e530d486989909249b8c821
d977698543c6266094eecdd8817ba371e26077dd7faece69c4fe4c4a07ff32b0

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-ginger-hammer-326 (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-ginger-hammer-326 across your stack and pipelines.

  2. If you installed it — respond

    Remove elf-stats-ginger-hammer-326 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-ginger-hammer-326 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-ginger-hammer-326 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-ginger-hammer-326 on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06199

Credits

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

Detect & block this

O3 blocks elf-stats-ginger-hammer-326-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-ginger-hammer-326 (npm) malicious package — MAL-2025-191982 | O3 Security