MAL-2026-12725 Malicious code in devplatform-nx-pvm (npm)
Malicious package
Published
MAL-2026-12725 is a malicious package: devplatform-nx-pvm (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12725/ (Markdown: https://insights.sbomify.com/MAL-2026-12725/index.md)
- Package
- devplatform-nx-pvm
- Registry
- npm
What is MAL-2026-12725?
MAL-2026-12725 is a malicious package in devplatform-nx-pvm, published on 5 Aug 2026.
Official description
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.
What should I do about MAL-2026-12725?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.