statist-browser-typed-client-coretech.web.metricsnpm
statist-browser-typed-client-coretech.web.metrics is a confirmed malicious npm package (MAL-2026-12444) that typosquats a legitimate package to trick installs (malicious version 20.1.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-coretech.web.metrics (npm)
What this malware does
On require() of the package, init.js selects a platform-specific asset, fetches an opaque binary via https.get from one of three hardcoded Cloudflare workers.dev hosts whose names are reconstructed from split-string arrays (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev), writes it to /var/tmp or %TEMP% under a disguised name (.cache<rnd> on Unix, dotnet_diag_<rnd>.exe on Windows), chmods 0755, and spawns it detached via spawn('/bin/sh',['-c',fp+' &']) or spawn('cmd',...). A DNS-TXT fallback channel resolves numbered subdomains under dl.well1.site (also assembled from fragmented array joins) and base64-decodes the concatenated TXT records when HTTPS retrieval fails. A hidden stamp file (.analytics_state) with a ~6.3-hour TTL throttles re-execution to establish recurring background execution, and the code short-circuits only on well-known opt-out envs (DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK), impersonating legitimate telemetry artifacts. The package name and telemetry cover story do not match the observed behavior: fetching opaque attacker bytes and executing them detached is a canonical binary-runner dropper.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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-coretech.web.metrics (version 20.1.8). 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-coretech.web.metrics across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-coretech.web.metrics is a typosquat — you almost certainly intended a legitimately-named package. Remove statist-browser-typed-client-coretech.web.metrics, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If statist-browser-typed-client-coretech.web.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-coretech.web.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-coretech.web.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.