statist-browser-typed-client-twork.tsales.nitro.metricsnpm
statist-browser-typed-client-twork.tsales.nitro.metrics is a confirmed malicious npm package (MAL-2026-12455) that executes malicious code on install (malicious version 20.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-twork.tsales.nitro.metrics (npm)
What this malware does
On require(), index.js loads shim.js which selects a platform-specific payload path, fetches a native binary from Cloudflare Workers subdomains whose hostnames are assembled at runtime from string-array fragments joined with.join(""), or falls back to a DNS-TXT covert channel that queries c.<domain> and N.<domain> and base64-decodes the concatenated TXT records into binary. The retrieved bytes are written to /var/tmp or %TEMP% under a disguised name (.cache<rand> on Unix, dotnet_diag_<rand>.exe on Windows), chmod'd to 0o755, and spawned detached via /bin/sh -c or cmd /c start. There is no pinning, no hash or signature verification, and the delivery hosts are anonymous Cloudflare Workers subdomains and a DNS-TXT channel — not a publisher-owned release surface. The hostname obfuscation and TXT-record covert channel are inconsistent with any legitimate observability or telemetry function.
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-browser-typed-client-twork.tsales.nitro.metrics (version 20.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging statist-browser-typed-client-twork.tsales.nitro.metrics across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-twork.tsales.nitro.metrics 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-browser-typed-client-twork.tsales.nitro.metrics 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-browser-typed-client-twork.tsales.nitro.metrics 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-browser-typed-client-twork.tsales.nitro.metrics-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.