# MAL-2026-13263: Malicious code in devplatform-spa-use-track (npm)


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

## What is MAL-2026-13263?

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

### Official description

On require() of the package, index.js loads _polyfill.js which fetches a platform-specific binary from one of four Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with DNS TXT fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. Hostnames are assembled at runtime from split string fragments and child_process is loaded via require("child_"+"process") to evade static substring scanning. The downloaded binary is written to /tmp or the Windows Temp directory under a disguised name (.cache_<hex> on Linux, dotnet_diag_<hex>.exe on Windows), chmod 0755 is applied through a computed "chmod"+"Sync" property lookup, and the file is spawned detached via /bin/sh -c or cmd.exe /c start /b. The package's advertised purpose is a trivial SPA tracking helper, which does not require any of this behavior. A second file, lib/telemetry.js (~81 KB, styled as a Sentry-like analytics SDK), contains an independent copy of the same fetch/chmod/spawn dropper primitives and ships as an alternate payload path in the tarball. The destination hosts are attacker-controlled, publisher-mismatched, and mutable; the executed bytes are opaque and unverified.

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

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

## Sources

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

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