statist-browser-typed-client-hra.workplacer.eventsnpm
statist-browser-typed-client-hra.workplacer.events is a confirmed malicious npm package (MAL-2026-12045) that executes malicious code on install (malicious version 20.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-hra.workplacer.events (npm)
What this malware does
On require of the package's main entry (index.js), polyfill.js downloads a platform-specific binary from one of several hosts whose names are reconstructed at runtime by joining string fragments (resolving to oob-worker.cf102-baf.workers.dev and similar Cloudflare Workers subdomains), with a DNS TXT-record fallback resolving to *.dl.well1.site. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start. Host and API names (child_process, chmodSync) are split across array literals and reassembled at runtime to evade static analysis. A sibling file lib/telemetry.js, labeled as an Analytics SDK, ships the same dropper primitives (detached shell spawn of a written file, chmod 0755, base64 chunk assembly, DNS-based service discovery) as an alternate loader. The package advertises itself as an event-emitter client, and the fetched binaries have disguised names (cache file, dotnet_diag) unrelated to that stated purpose. The result is arbitrary remote code execution on any machine that installs or imports this package.
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-hra.workplacer.events (version 20.9.1). 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-hra.workplacer.events across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-hra.workplacer.events 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-hra.workplacer.events 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-hra.workplacer.events 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-hra.workplacer.events-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.