statist-browser-typed-client-mb.product.analyticsnpm
statist-browser-typed-client-mb.product.analytics is a confirmed malicious npm package (MAL-2026-12211) that opens a backdoor for remote access (malicious version 20.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-mb.product.analytics (npm)
What this malware does
On require() of the package, index.js loads bridge.js which detects the host platform, fetches a native binary from a rotating list of hardcoded Cloudflare workers.dev endpoints (with a DNS-TXT chunked base64 fallback via well1.site subdomains), writes it to /tmp or %TEMP% under a masquerading name such as dotnet_diag<hex>.exe or.cache_<hex>, chmods 0755, and spawns it detached via cmd.exe or /bin/sh. The C2 hostnames and payload paths are assembled at runtime through array-join string-splitting to evade static analysis, and the require of _bridge.js is wrapped in a try/catch that silently swallows errors. No hash or signature verification is performed on the downloaded binary. The result is full-host remote code execution on any machine that installs or 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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind 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-mb.product.analytics (version 20.1.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-mb.product.analytics across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-mb.product.analytics establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If statist-browser-typed-client-mb.product.analytics 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-mb.product.analytics 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-mb.product.analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.