Which versions of devplatform-cli-spa are malicious?

The following npm versions of devplatform-cli-spa are flagged malicious: 35.7.8. Treat any of these as compromised.

How do I remediate devplatform-cli-spa if I installed it?

devplatform-cli-spa establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed devplatform-cli-spa — how do I know if it already compromised me?

If devplatform-cli-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.

Is devplatform-cli-spa part of a known attack campaign?

Yes — devplatform-cli-spa is associated with the IN-MAL-2026-015070 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find devplatform-cli-spa across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-cli-spa (version 35.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-cli-spa across your stack and pipelines.

Malicious package

devplatform-cli-spanpm

devplatform-cli-spa is a confirmed malicious npm package (MAL-2026-12704) that opens a backdoor for remote access (malicious version 35.7.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-cli-spa (npm)

MAL-2026-12704

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall devplatform-cli-spa

What this malware does

On require('devplatform-cli-spa'), index.js loads support.js which selects a payload by OS and architecture, downloads a native binary over HTTPS from string-obfuscated Cloudflare Workers hostnames (oob-worker.cf1-01-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT base64 fallback served from *.dl.wel1.ru. The fetched bytes are written to /tmp/.cache<rnd> on Unix or %TEMP%/dotnet_diag_<rnd>.exe on Windows, chmod'd to 0755, and executed detached via spawn('/bin/sh', ['-c',...]) or spawn('cmd', ['/c', 'start',...]). The C2 hostnames and the DNS fallback domains are assembled at runtime by joining split string fragments (_NODES and _DNS_HOSTS arrays) to evade static string matching. The Windows drop path uses a 'dotnet_diag' decoy filename, and a stamp file gates re-runs across installs.

Malicious versions

1 flagged

35.7.8

Indicators of compromise (SHA-256)

1bb41284069ba395bf67ceb847dc579c7a79c753ea89107116e91559ebbece2a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-cli-spa (version 35.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-cli-spa across your stack and pipelines.
If you installed it — respond
devplatform-cli-spa establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-cli-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-cli-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

No. devplatform-cli-spa on npm has been identified as a malicious package (version 35.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015070

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-cli-spa-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database