Which versions of devplatform-spa-errors are malicious?

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

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

Remove devplatform-spa-errors 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.

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

If devplatform-spa-errors 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-spa-errors part of a known attack campaign?

Yes — devplatform-spa-errors is associated with the IN-MAL-2026-016990 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-spa-errors 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-spa-errors (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-errors across your stack and pipelines.

Malicious package

devplatform-spa-errorsnpm

devplatform-spa-errors is a confirmed malicious npm package (MAL-2026-13545) 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-errors (npm)

MAL-2026-13545

Immediate action

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

npm uninstall devplatform-spa-errors

What this malware does

On require() of the package, index.js unconditionally loads loader.js, which selects a platform-specific payload path, fetches an opaque native binary from string-concatenated Cloudflare Workers subdomains (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT chunked fallback channel to *.dl.wel1.ru, writes the bytes to a temp path disguised as dotnet_diag<tok>.exe on Windows or.cache_<tok> on POSIX, chmods it to 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe /c start. Hostnames and dropped filenames are assembled at runtime from split-string arrays and framed with Analytics/telemetry SDK cover strings. lib/telemetry.js contains a duplicate copy of the dropper logic (base64-decoded chunks, chmodSync 0755, cp.spawn('/bin/sh', ['-c', filePath + ' &'])) inside a decoy Sentry-like observability module. The package delivers attacker-controlled native code to the installer's host on module load, with no integrity verification and active string obfuscation to evade review.

Malicious versions

1 flagged

35.5.7

Indicators of compromise (SHA-256)

5cb27f42d7166d8e64db0a98a48a18f64817d801d1e4b6250c62320f08143d59

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-spa-errors (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-errors across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-errors 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-errors 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-errors 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-spa-errors on npm has been identified as a malicious package (version 35.5.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016990

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-errors-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database