Which versions of devplatform-nx-spa are malicious?

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

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

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

If devplatform-nx-spa was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — devplatform-nx-spa is associated with the IN-MAL-2026-015051 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-nx-spa across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for devplatform-nx-spa (version 35.8.7).

Malicious package

devplatform-nx-spanpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in devplatform-nx-spa (npm)

MAL-2026-12727

Immediate action

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

npm uninstall devplatform-nx-spa

What this malware does

On require of the package, index.js loads support.js, whose top-level init() selects a platform-specific asset, downloads a native binary from one of four Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev through cf103), and falls back to reconstructing the binary from base64-encoded DNS TXT records under *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) when HTTPS fails. The fetched bytes are written to /var/tmp (POSIX) or %TEMP% (Windows) under a cover filename ('dotnet_diag<rand>.exe' or '.cache_<rand>'), chmod 0755'd on POSIX, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames are assembled at runtime via.join("") on split string literals to evade static analysis, and a state file named '.analytics_state' is used as cover. A sibling lib/telemetry.js is unreferenced in this version but reimplements the same drop-and-exec primitives behind an 'analytics SDK' framing.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

b8fa5cc0213b5b28609ba1035cb25dd701d3e8690f25b5a3b4dc37f5139fa740

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for devplatform-nx-spa (version 35.8.7).
If you installed it — respond
Remove devplatform-nx-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-nx-spa was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015051

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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