# MAL-2026-12785: Malicious code in devplatform-spa-tokens (npm)


- **Type:** Malicious package
- **Package:** `devplatform-spa-tokens` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-67wj-rrpv-vxwq

## What is MAL-2026-12785?

MAL-2026-12785 is a malicious package in devplatform-spa-tokens, published on 5 Aug 2026. 

### Official description

On require(), index.js loads _support.js, which assembles Cloudflare Workers hostnames (oob-worker.cf*.workers.dev) and fallback domain sdk.dl.wel1.ru at runtime from split string arrays joined via.join(""), downloads a platform-specific binary from those hosts (with a DNS TXT chunked fallback via c.<domain>/i.<domain> records when HTTPS is blocked), writes the payload to a temp path with a disguised name (e.g. dotnet_diag_<rand>.exe,.cache_<rand>), chmods 0755 on POSIX, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). Execution is gated by DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env vars and a /tmp/.analytics_state cache, framing the dropper as analytics. The advertised TokenManager API is a decoy — no relation to the download-and-execute behavior. Destination hosts are anonymous workers.dev / lookalike infrastructure, not the package's stated purpose or publisher.

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

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

## Sources

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

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