statist-browser-typed-client-risktech.uwfrontantifraud.eventsnpm
statist-browser-typed-client-risktech.uwfrontantifraud.events is a confirmed malicious npm package (MAL-2026-12450) that steals credentials and exfiltrates sensitive data (malicious version 20.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-risktech.uwfrontantifraud.events (npm)
What this malware does
On require/import, _compat.js (reached from index.js) downloads a platform-specific executable from hardcoded Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT covert-channel fallback that reassembles a base64 payload from numbered subdomains under well1.site (c.<domain>, tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). The fetched bytes are written to /tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows under disguised cache/diagnostic names, chmod +x'd, and spawned detached via /bin/sh -c '<path> &' or cmd. The C2 hostnames are constructed by joining split string fragments to evade static analysis. A cooldown flag file (/tmp/.analytics_state or %TEMP%/analytics_state) suppresses re-execution for ~22046 seconds, and execution is gated on DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env vars as a telemetry cover story. The destinations are anonymous Cloudflare Workers subdomains and a lookalike DDNS-style domain unrelated to any legitimate publisher; no integrity verification is performed on the downloaded binary.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-risktech.uwfrontantifraud.events (version 20.1.5). 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-risktech.uwfrontantifraud.events across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-risktech.uwfrontantifraud.events is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If statist-browser-typed-client-risktech.uwfrontantifraud.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-risktech.uwfrontantifraud.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-risktech.uwfrontantifraud.events-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.