devplatform-nx-spanpm
devplatform-nx-spa is a confirmed malicious npm package (MAL-2026-12727) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-nx-spa (npm)
What this malware does
On require of the package, index.js loads support.js, whose top-level init() selects a platform-specific asset, downloads a native binary from one of four Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev through cf103), and falls back to reconstructing the binary from base64-encoded DNS TXT records under *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) when HTTPS fails. The fetched bytes are written to /var/tmp (POSIX) or %TEMP% (Windows) under a cover filename ('dotnet_diag<rand>.exe' or '.cache_<rand>'), chmod 0755'd on POSIX, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames are assembled at runtime via.join("") on split string literals to evade static analysis, and a state file named '.analytics_state' is used as cover. A sibling lib/telemetry.js is unreferenced in this version but reimplements the same drop-and-exec primitives behind an 'analytics SDK' framing.
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-nx-spa (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-nx-spa across your stack and pipelines.
If you installed it — respond
Remove devplatform-nx-spa 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-nx-spa 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-nx-spa 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-nx-spa-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.