devplatform-spa-use-tracknpm
devplatform-spa-use-track is a confirmed malicious npm package (MAL-2026-13263) that executes malicious code on install (malicious version 35.5.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-use-track (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-spa-use-track (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-use-track across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-use-track from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If devplatform-spa-use-track was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks devplatform-spa-use-track before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks devplatform-spa-use-track-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.