statist-browser-typed-client-test.jumpwork.circuitbreakernpm
statist-browser-typed-client-test.jumpwork.circuitbreaker is a confirmed malicious npm package (MAL-2026-12046) that executes malicious code on install (malicious version 20.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-test.jumpwork.circuitbreaker (npm)
What this malware does
On require() of the package's main entry, _compat.js runs as a side effect: it selects a per-platform payload, fetches a native binary over HTTPS from one of several Cloudflare Workers hosts whose names are reconstructed at runtime by joining small string fragments (e.g. oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), writes it to /tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c "<file> &" or cmd /c start /b. A DNS-TXT covert channel provides a fallback delivery path against *.dl.well1.site (tin/tina/ldr/win subdomains), retrieving a count record at c.<domain> and then base64-encoded chunks from <i>.<domain> that are concatenated and executed. A second, larger duplicate of the same dropper (dynamic child_"+"process require, chmod-plus-detached-spawn, DNS discovery, base64 buffer assembly) is shipped as lib/telemetry.js in the tarball. Hostname string-array obfuscation and decoy filenames (dotfile cache, dotnet_diag_*.exe) indicate intentional evasion; installing or importing this package executes attacker-controlled native code on the developer's machine.
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-test.jumpwork.circuitbreaker (version 20.8.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-test.jumpwork.circuitbreaker across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-test.jumpwork.circuitbreaker 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-test.jumpwork.circuitbreaker 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-test.jumpwork.circuitbreaker 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-test.jumpwork.circuitbreaker-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.