devplatform-spa-plugin-analyticsnpm
devplatform-spa-plugin-analytics is a confirmed malicious npm package (MAL-2026-12760) that executes malicious code on install (malicious version 35.5.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-analytics (npm)
What this malware does
[email protected] advertises itself as an analytics library, but on require() its main entry loads adapter.js which downloads a platform-specific executable from obfuscated Cloudflare Workers origins (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), writes it to /tmp or %TEMP% under a hidden name (e.g..cache<hex>, dotnet_diag_<hex>.exe), chmods it 0o755, and spawns it detached via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or spawn('cmd',...). Destination hostnames and the DNS fallback domain are assembled at runtime by array.join to evade static extraction (e.g. ['oob-w','orker','.cf101-adf.worker','s.dev'].join('')). A DNS-TXT covert channel provides fallback delivery: the loader resolves TXT records under c.<domain> and <i>.<domain> at *.dl.wel1.ru, concatenates base64 chunks, and writes and executes the reassembled binary. No native source ships in the package, no build step exists, and the fetched bytes are opaque and unrelated to any publisher endpoint. The behavior fires automatically on require() of the package, producing full-host code execution on the installer under an attacker-controlled binary.
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-analytics (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-analytics across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-analytics 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-analytics 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-analytics 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-analytics-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.