# MAL-2026-12760: Malicious code in devplatform-spa-plugin-analytics (npm)


- **Type:** Malicious package
- **Package:** `devplatform-spa-plugin-analytics` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12760?

MAL-2026-12760 is a malicious package in devplatform-spa-plugin-analytics, published on 5 Aug 2026. 

### Official description

devplatform-spa-plugin-analytics@35.5.7 advertises itself as an analytics library, but on require() its main entry loads _adapter.js which downloads a platform-specific executable from obfuscated Cloudflare Workers origins (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), writes it to /tmp or %TEMP% under a hidden name (e.g..cache_<hex>, dotnet_diag_<hex>.exe), chmods it 0o755, and spawns it detached via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or spawn('cmd',...). Destination hostnames and the DNS fallback domain are assembled at runtime by array.join to evade static extraction (e.g. ['oob-w','orker','.cf101-adf.worker','s.dev'].join('')). A DNS-TXT covert channel provides fallback delivery: the loader resolves TXT records under c.<domain> and <i>.<domain> at *.dl.wel1.ru, concatenates base64 chunks, and writes and executes the reassembled binary. No native source ships in the package, no build step exists, and the fetched bytes are opaque and unrelated to any publisher endpoint. The behavior fires automatically on require() of the package, producing full-host code execution on the installer under an attacker-controlled binary.

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

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-12760 is a malicious package: devplatform-spa-plugin-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-12760/ (Markdown: https://insights.sbomify.com/MAL-2026-12760/index.md)
```

## Sources

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

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