Which versions of devplatform-spa are malicious?

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

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

Remove devplatform-spa 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 — how do I know if it already compromised me?

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

Yes — devplatform-spa is associated with the IN-MAL-2026-015020 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 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 (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa across your stack and pipelines.

Malicious package

devplatform-spanpm

devplatform-spa is a confirmed malicious npm package (MAL-2026-12754) that executes malicious code on install (malicious version 35.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa (npm)

MAL-2026-12754

Immediate action

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

npm uninstall devplatform-spa

What this malware does

On require('devplatform-spa'), index.js loads loader.js which downloads an OS-specific binary from Cloudflare Workers endpoints whose hostnames are assembled via string-array joins (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record fallback channel across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe in _loader.js line 121-127. The loader is invoked unconditionally from index.js via try{require('./_loader')}catch{}, so the drop-and-execute runs on every require. Cover-story elements include a.analytics_state file, a no-op _l logging stub, and DISABLE_TELEMETRY/DO_NOT_TRACK opt-out checks that masquerade the behavior as telemetry.

Malicious versions

1 flagged

35.1.4

Indicators of compromise (SHA-256)

297ea05a85bad5f3af2ead77745d792c055efc94b9b58726fe3ee499821c745c

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 (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa 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 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 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 on npm has been identified as a malicious package (version 35.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015020

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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