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)
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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.
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.
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.
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
Campaign
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.