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

elf-stats-mistletoe-sparkler-211npm

Malicious code in elf-stats-mistletoe-sparkler-211 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192099
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall elf-stats-mistletoe-sparkler-211

What this malware does

The package elf-stats-mistletoe-sparkler-211 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'elf-stats-mistletoe-sparkler-211' @ 9999.1.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

3 flagged
9999.0.09999.1.19999.1.3

Indicators of compromise (SHA-256)

47252656d84badb7e05ccaeaf93790d0fb12cabd9049756bc91814e3e3c7e2c4
c81f46b43dd8df82428a84fe16b8a8204069ad9a548c1996b62abd7e95b8b870
a0a01ab665ce993aab928a62ed3e3e5b42dc9ef906dcce1bef8471e13af48537

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-mistletoe-sparkler-211 (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-mistletoe-sparkler-211 across your stack and pipelines.

  2. If you installed it — respond

    Remove elf-stats-mistletoe-sparkler-211 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-mistletoe-sparkler-211 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-mistletoe-sparkler-211 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-mistletoe-sparkler-211 on npm has been identified as a malicious package (versions 9999.0.0, 9999.1.1, 9999.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06243

Credits

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

Detect & block this

O3 blocks elf-stats-mistletoe-sparkler-211-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-mistletoe-sparkler-211 (npm) malicious package — MAL-2025-192099 | O3 Security