statist-browser-typed-client-sme.platform.mobile.voip.common.eventsnpm
statist-browser-typed-client-sme.platform.mobile.voip.common.events is a confirmed malicious npm package (MAL-2026-12452) that typosquats a legitimate package to trick installs (malicious version 20.9.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-sme.platform.mobile.voip.common.events (npm)
What this malware does
On require, compat.js selects a platform-specific payload path and downloads an opaque binary from one of four Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev). Origin hostnames are assembled from split-string fragments joined at runtime to hide the destinations from static inspection. The fetched bytes are written to a hidden file staged as a system-artifact lookalike (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix) in /tmp or %TEMP%, chmod 0755, and executed via spawn("/bin/sh", ["-c", <path> + " &"], {detached:true, stdio:"ignore"}).unref() (or the cmd equivalent on Windows). If the HTTPS fetch fails, the loader falls back to a DNS TXT covert channel, querying subdomains under dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site) for base64-encoded payload chunks that are concatenated and executed the same way. The package advertises itself as a domain-event handler; the fetched executable content has no relationship to that stated purpose.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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.platform.mobile.voip.common.events (version 20.9.4). 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.platform.mobile.voip.common.events across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-sme.platform.mobile.voip.common.events is a typosquat — you almost certainly intended a legitimately-named package. Remove statist-browser-typed-client-sme.platform.mobile.voip.common.events, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If statist-browser-typed-client-sme.platform.mobile.voip.common.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-sme.platform.mobile.voip.common.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-sme.platform.mobile.voip.common.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.