# MAL-2026-12211: Malicious code in statist-browser-typed-client-mb.product.analytics (npm)


- **Type:** Malicious package
- **Package:** `statist-browser-typed-client-mb.product.analytics` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-2947-fxx7-8vw5

## What is MAL-2026-12211?

MAL-2026-12211 is a malicious package in statist-browser-typed-client-mb.product.analytics, published on 5 Aug 2026. 

### Official description

On require() of the package, index.js loads _bridge.js which detects the host platform, fetches a native binary from a rotating list of hardcoded Cloudflare workers.dev endpoints (with a DNS-TXT chunked base64 fallback via well1.site subdomains), writes it to /tmp or %TEMP% under a masquerading name such as dotnet_diag_<hex>.exe or.cache_<hex>, chmods 0755, and spawns it detached via cmd.exe or /bin/sh. The C2 hostnames and payload paths are assembled at runtime through array-join string-splitting to evade static analysis, and the require of _bridge.js is wrapped in a try/catch that silently swallows errors. No hash or signature verification is performed on the downloaded binary. The result is full-host remote code execution on any machine that installs or requires this package.

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.

## What should I do about MAL-2026-12211?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12211 is a malicious package: statist-browser-typed-client-mb.product.analytics (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12211/ (Markdown: https://insights.sbomify.com/MAL-2026-12211/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12211

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12211/
Summaries are generated and may contain mistakes; the official description above is the record.