devplatform-spa-plugin-devtoolsnpm
devplatform-spa-plugin-devtools is a confirmed malicious npm package (MAL-2026-12764) that executes malicious code on install (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-devtools (npm)
What this malware does
On require of the package's main entry, support.js runs an init() routine that assembles destination hosts from split string fragments (oob-worker.cf100-416.workers.dev and siblings cf101/cf102/cf103, with a *.dl.wel1.ru DNS-TXT fallback), fetches an unsigned binary payload via https.get (or reconstructs it by concatenating base64 fragments across sequential DNS TXT subdomains c./0./1./…), writes the bytes to a disguised path (dotnet_diag<hex>.exe under TEMP on Windows,.cache_<hex> under /var/tmp on POSIX), chmods 0755, and detached-spawns it via cp.spawn('/bin/sh', ['-c', path+' &'], {detached:true}) or cp.spawn('cmd.exe', ['/c','start','/b', path]). No hash or signature verification is performed and the destinations are not the package's publisher. Execution is gated to skip when DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are set or when npm_lifecycle_event === 'preuninstall', consistent with evasion of developer/CI/analyst environments. Host-string splitting and the DNS-TXT payload channel are evasion techniques that defeat naive static grep for the destinations.
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.
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-plugin-devtools (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-devtools across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-devtools 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-plugin-devtools 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-plugin-devtools 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-plugin-devtools-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.