statist-browser-typed-client-mb.product.operationsnpm
statist-browser-typed-client-mb.product.operations is a confirmed malicious npm package (MAL-2026-12448) that executes malicious code on install (malicious version 20.4.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-mb.product.operations (npm)
What this malware does
index.js unconditionally requires./bridge on module load. bridge.js selects an OS/arch-specific payload URL from string-array-concatenated hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), downloads a binary over HTTPS with a DNS TXT chunked-base64 fallback via *.dl.well1.site, writes it to /var/tmp or %TEMP% under a disguised name (dotnet_diag<hex>.exe /.cache<hex>), chmods it 0755, and detached-spawns it via /bin/sh -c "<path> &" or cmd.exe /c start /b. No hash or signature verification. Destination hostnames are assembled at runtime by joining split string arrays to evade static analysis, and a written state file plus environment-variable opt-outs (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and comments referencing "SHA-256 integrity check" and "session tracking" frame the drop as telemetry, which does not match the package's stated Operations SDK purpose.
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-mb.product.operations (version 20.4.9). 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.operations across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-mb.product.operations 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-mb.product.operations 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.operations 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.operations-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.