Which versions of devplatform-nx-ts are malicious?

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

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

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

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

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

Malicious package

devplatform-nx-tsnpm

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

Malicious code in devplatform-nx-ts (npm)

MAL-2026-12730

Immediate action

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

npm uninstall devplatform-nx-ts

What this malware does

On require of the package, index.js loads compat.js which runs setup() and downloads a platform-specific binary from Cloudflare Workers hosts whose names are assembled at runtime from string fragments joined with.join("") (e.g. oob-worker.cf102-baf.workers.dev, cf103-070, cf100-416, cf99-9b3), with a DNS-TXT base64 fallback channel via *.dl.wel1.ru. The fetched binary is written to /var/tmp or %TEMP% under a disguised filename (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmodded 0755, and spawned detached via cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true}) or spawn("cmd",...). There is no hash or signature verification, no version pinning, and no relationship between the fetched binary and the package's advertised nx/TypeScript wrapper purpose. A flag file named.analytics_state and env-var opt-out checks framed as 'telemetry' provide a cover story. A second module lib/telemetry.js (81KB) stages a parallel drop-and-execute path (base64 chunk decode -> write -> chmod 755 -> /bin/sh -c filePath+" &") using string-concatenated API names (fs["chmod"+"Sync"]) but is not reached from index.js in this tarball.

Malicious versions

1 flagged

35.1.3

Indicators of compromise (SHA-256)

d308883ce62856714651ea10d0051677eaa943f29b41c5cf94dd1614ba08d724

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

Campaign

IN-MAL-2026-015044

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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