Which versions of devplatform-nx-pvm are malicious?

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

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

devplatform-nx-pvm is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed devplatform-nx-pvm — how do I know if it already compromised me?

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

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

Malicious package

devplatform-nx-pvmnpm

devplatform-nx-pvm is a confirmed malicious npm package (MAL-2026-12725) that steals credentials and exfiltrates sensitive data (malicious version 35.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-nx-pvm (npm)

MAL-2026-12725

Immediate action

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

npm uninstall devplatform-nx-pvm

What this malware does

On require() of devplatform-nx-pvm, compat.js fetches a platform-specific binary over HTTPS from hardcoded hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), writes it to /tmp or %TEMP% under a disguised filename (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh or cmd. The C2 hostnames are assembled from split string arrays (e.g. ["oob-worker.cf100-416.work","ers.dev"].join("")) to evade static scanners, and a cover file named analytics_state is used as a run marker. If the HTTPS fetches fail, the code falls back to a DNS TXT covert channel against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru and net.dl.wel1.ru, retrieving a chunk count from c.<domain> and base64-encoded payload chunks from N.<domain>, concatenating and decoding them, then executing the resulting binary. The dropper is skipped when specific telemetry opt-out environment variables are set, further indicating stealth. The package presents itself as a trivial library shim, and index.js unconditionally requires _compat, so installing and importing the package auto-executes the attacker-controlled binary on the installer's machine.

Malicious versions

1 flagged

35.2.9

Indicators of compromise (SHA-256)

58df39bb6ab40bc06f0c7db6a10753e81979cae9692633b51a33089ff6d28aa4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-nx-pvm (version 35.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-nx-pvm across your stack and pipelines.
If you installed it — respond
devplatform-nx-pvm is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If devplatform-nx-pvm 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-pvm 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-pvm on npm has been identified as a malicious package (version 35.2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015060

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-nx-pvm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database