Which versions of elf-stats-gingersnap-sparkler-768 are malicious?

The following npm versions of elf-stats-gingersnap-sparkler-768 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate elf-stats-gingersnap-sparkler-768 if I installed it?

Remove elf-stats-gingersnap-sparkler-768 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.

I already installed elf-stats-gingersnap-sparkler-768 — how do I know if it already compromised me?

If elf-stats-gingersnap-sparkler-768 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find elf-stats-gingersnap-sparkler-768 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for elf-stats-gingersnap-sparkler-768 (version 1.0.1).

Malicious package

elf-stats-gingersnap-sparkler-768npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

elf-stats-gingersnap-sparkler-768 is a confirmed malicious npm package (MAL-2025-192057) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in elf-stats-gingersnap-sparkler-768 (npm)

MAL-2025-192057

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall elf-stats-gingersnap-sparkler-768

What this malware does

The package elf-stats-gingersnap-sparkler-768 was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

225139bc6c7d1eee91d68d13be40ff78b442a72ed2d5a3dfb7245aadcba9d211

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for elf-stats-gingersnap-sparkler-768 (version 1.0.1).
If you installed it — respond
Remove elf-stats-gingersnap-sparkler-768 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.
Did it already run?
If elf-stats-gingersnap-sparkler-768 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. elf-stats-gingersnap-sparkler-768 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks elf-stats-gingersnap-sparkler-768-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database