statist-browser-typed-client-sme.rko.tariffs.webnpm
statist-browser-typed-client-sme.rko.tariffs.web is a confirmed malicious npm package (MAL-2026-13379) that opens a backdoor for remote access (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-sme.rko.tariffs.web (npm)
What this malware does
On require() of this package, index.js loads compat.js which selects a platform-specific payload path, fetches an opaque binary over HTTPS from one of three string-obfuscated *.workers.dev hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), and falls back to a DNS TXT covert channel on *.dl.well1.site (tin/tina/ldr/win.dl.well1.site) if HTTPS fails. The fetched bytes are written to a temp file with a cover-story name (dotnet_diag.exe on Windows, /var/tmp/.cache_ on Unix), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start. C2 hostnames are assembled at runtime from split-string arrays joined with '' to evade static analysis. There is no signature or hash verification, and the fetched binary is unrelated to the package's stated 'web adapter' purpose. A cooldown marker is written to suppress re-execution.
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-sme.rko.tariffs.web (version 20.3.8). 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-sme.rko.tariffs.web across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-sme.rko.tariffs.web 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-sme.rko.tariffs.web 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-sme.rko.tariffs.web 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-sme.rko.tariffs.web-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.