devplatform-spa-devtoolsnpm
devplatform-spa-devtools is a confirmed malicious npm package (MAL-2026-12756) that executes malicious code on install (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-devtools (npm)
What this malware does
On require('devplatform-spa-devtools'), index.js loads runtime.js which downloads a platform-specific executable from obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) whose hostnames are reassembled from split string arrays at runtime. The payload is written to disk under masquerading names (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmod'd 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true,stdio:'ignore'}).unref() with no hash or signature verification. A fallback path uses DNS TXT record lookups against *.dl.wel1.ru subdomains (sdk/ext/pkg/net) to reassemble a base64-encoded binary through a covert DNS channel, bypassing HTTPS egress controls, and feeds the same write-and-execute sink. Environment-variable gates named after common telemetry opt-outs (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a freshness marker suppress repeat execution, providing a telemetry cover story. The workers.dev subdomains and the wel1.ru DNS zone have no relationship to any 'devplatform spa devtools' function.
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-devtools (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-devtools across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-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-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-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-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.