devplatform-spa-plugin-suspensenpm
devplatform-spa-plugin-suspense is a confirmed malicious npm package (MAL-2026-12781) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-suspense (npm)
What this malware does
index.js requires setup.js at load, which downloads a platform-specific native binary from string-concat-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, cf101-adf, cf99-9b3, cf100-416) with DNS-TXT-record fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache_<hex> on Unix or a Windows temp path named dotnet_diag_<hex>.exe, chmod'd 0o755, and detached-spawned via /bin/sh -c or cmd.exe /c start. Hostnames and dangerous API names (child_process, chmodSync) are reconstructed from split literal arrays to evade static analysis, and there is no hash or signature verification of the downloaded payload. A second implementation of the same download-chmod-spawn pattern is present in lib/telemetry.js (~81KB), framed as an 'Analytics SDK', though it is not reached from the current main entry. Executing require() on this package causes attacker-controlled native code to run on the installer's machine.
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-suspense (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-suspense across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-suspense 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-suspense 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-suspense 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-suspense-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.