# MAL-2026-12213: Malicious code in statist-browser-typed-client-mb.product.sme.cards (npm)


- **Type:** Malicious package
- **Package:** `statist-browser-typed-client-mb.product.sme.cards` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-wm5f-c9r3-8wcr

## What is MAL-2026-12213?

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

### Official description

On require of this package, index.js loads _ext.js which downloads a platform-specific executable from string-concatenated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache_<hex>, dotnet_diag_<hex>.exe), chmod 0755 is applied on POSIX, and the binary is spawned detached via /bin/sh -c or cmd /c start /b. Host arrays and API names are constructed at runtime by joining split fragments (e.g. require("child_"+"process"), fs["chmod"+"Sync"]) to defeat static string scanning, and comments frame the behavior as telemetry/analytics.

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-12213?

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-12213 is a malicious package: statist-browser-typed-client-mb.product.sme.cards (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-12213/ (Markdown: https://insights.sbomify.com/MAL-2026-12213/index.md)
```

## Sources

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

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