statist-browser-typed-client-mb.product.mclaccount (npm) · Malicious Code
Affects statist-browser-typed-client-mb.product.mclaccountSource GCVE Database
Malicious package : remove statist-browser-typed-client-mb.product.mclaccount and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12447
What to do
Remove statist-browser-typed-client-mb.product.mclaccount from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmstatist-browser-typed-client-mb.product.mclaccount | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1381b3c1cd52acc110406d4609b7afea6e0681e3fe1259fcff0cd0a819aacabc) On require, index.js loads _loader.js which selects a platform-specific binary path, fetches bytes from obfuscated Cloudflare Workers endpoints (oob-worker.cf102-baf.workers.dev, cf100-416/cf103-070/cf99-9b3.workers.dev) with a DNS TXT-record fallback channel across numbered subdomains of dl.well1.site (tin, tina, ldr, win) that reassembles a base64 payload. The downloaded bytes are written to /tmp or %TEMP% under disguised names (.cache_<rand>, dotnet_diag_<rand>.exe), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames and API names are reconstructed via split-string joins (e.g. ['tin.','dl.well1.si','te'].join(''), require('child_'+'process')) to evade static analysis. A parallel implementation of the same dropper is shipped as lib/telemetry.js under an 'analytics SDK' cover story, with identical DNS-TXT reassembly, chmod 0755, and detached /bin/sh execution. ## Source: ghsa-malware (21bc192595c845c8870559d0575b69c158b6441912ceed68a263730b683d180a) 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.