Which versions of stats-engine are malicious?

Every published version of stats-engine on npm is considered malicious. Remove the package entirely.

How do I remediate stats-engine if I installed it?

Remove stats-engine 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 stats-engine — how do I know if it already compromised me?

If stats-engine 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 stats-engine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stats-engine (all published versions).

Malicious package

stats-enginenpm

Advisory published Dec 3, 2025Updated Dec 3, 2025

stats-engine is a confirmed malicious npm package (MAL-2025-192258) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stats-engine (npm)

MAL-2025-192258

Immediate action

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

npm uninstall stats-engine

What this malware does

The package stats-engine was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

81d8d8781451e304c1c297f470171e086759a549dd97d397c6f87847c7e1417d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for stats-engine (all published versions).
If you installed it — respond
Remove stats-engine 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 stats-engine 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. stats-engine on npm has been identified as a malicious package (all published versions 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 stats-engine-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