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

elf-stats-festive-sparkler-275npm

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

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

What this malware does

The package elf-stats-festive-sparkler-275 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-festive-sparkler-275' @ 2.0.1 (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

7 flagged
1.0.11.0.21.0.31.0.42.0.02.0.12.0.2

Indicators of compromise (SHA-256)

e118633889a307914cb4954e0f154bf6e3369dad3901c57fec4a08667e7af4a8
f3adaeddf56adca42174e060e74d72cba7c7afff543772ffc7037f6329fe0359
458906fe6d41be31cecbaf8872f7fc8715d8f4a838373dee7798e5c3ce066bec
fd8ba0eb7e58cb06bc322ae50b4432eedb2f04ca0b5b2edc00dbb20418556248
c05aec9b15ceed4b03ab7714e2797a78ab68acb551897cfb24c0950391db6faa

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

  2. If you installed it — respond

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

Campaign

GHSA-cqjm-gc5c-7gh9RLMA-2025-06183

References

Credits

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

Detect & block this

O3 blocks elf-stats-festive-sparkler-275-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-festive-sparkler-275 (npm) malicious package — MAL-2025-192294 | O3 Security