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

statist-statist-corenpm

statist-statist-core is a confirmed malicious npm package (MAL-2026-12456) that executes malicious code on install (malicious version 20.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in statist-statist-core (npm)

MAL-2026-12456
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall statist-statist-core

What this malware does

index.js requires./setup on module load. setup.js assembles obfuscated destination hostnames from split string arrays, selects a platform-specific endpoint from four hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), downloads an opaque binary via https.get, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag_<suffix>.exe on Windows,.cache_<suffix> on Unix), chmods 0755, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). When HTTPS fetch fails, setup.js falls back to a DNS TXT-record channel under *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site): it queries a count record and then N chunk records, base64-decodes the concatenation, and executes the reconstructed payload — an evasion channel that bypasses HTTP egress filtering. The child_process module name and destination hostnames are runtime-assembled from split arrays to defeat static scanners; disguised filenames and an analytics/telemetry framing serve as cover. The fetch-and-execute path fires automatically whenever any consumer requires this package.

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.

Malicious versions

1 flagged
20.9.9

Indicators of compromise (SHA-256)

192fac66540fb5d3f4c376673ddd67a4e43053342e745e538f7ddcc08b0a9042
951066f8fd3f0cc78122046780b65659e2e22d1aa548afaeb26b8a8ca5bad739

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 statist-statist-core (version 20.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging statist-statist-core across your stack and pipelines.

  2. If you installed it — respond

    Remove statist-statist-core 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 statist-statist-core 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 statist-statist-core 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. statist-statist-core on npm has been identified as a malicious package (version 20.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014712GHSA-j362-x54r-m764

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks statist-statist-core-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.

Explore

statist-statist-core (npm) malicious package — MAL-2026-12456 | O3 Security