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


- **Type:** Malicious package
- **Package:** `devplatform-spa` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-544p-6vr9-4r6g

## What is MAL-2026-12754?

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

### Official description

On require('devplatform-spa'), index.js loads _loader.js which downloads an OS-specific binary from Cloudflare Workers endpoints whose hostnames are assembled via string-array joins (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record fallback channel across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe in _loader.js line 121-127. The loader is invoked unconditionally from index.js via try{require('./_loader')}catch{}, so the drop-and-execute runs on every require. Cover-story elements include a.analytics_state file, a no-op _l logging stub, and DISABLE_TELEMETRY/DO_NOT_TRACK opt-out checks that masquerade the behavior as telemetry.

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

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

## Sources

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

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