Which versions of devplatform-cli are malicious?

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

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

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

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

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

Malicious package

devplatform-clinpm

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

Malicious code in devplatform-cli (npm)

MAL-2026-12699

Immediate action

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

npm uninstall devplatform-cli

What this malware does

On require() of devplatform-cli, index.js loads adapter.js which assembles Cloudflare Workers hostnames from string-split fragments (e.g. ["oob-worker.cf","103-070.workers.d","ev"].join("")) with a DNS-TXT chunked-base64 fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, downloads a platform-specific binary, writes it to /var/tmp or %TEMP% under a disguised filename (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), calls fs.chmodSync(path, 0o755) on POSIX, and background-spawns it detached via cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true,stdio:"ignore"}) or cmd /c start /b. A sibling module lib/telemetry.js (81KB, framed as "Analytics SDK") duplicates the same fetch->write->chmod 0755->spawn /bin/sh pattern and further obfuscates dangerous APIs via require("child_"+"process") and fs["chmod"+"Sync"]. The destinations are anonymous serverless hosts unrelated to any documented publisher infrastructure, the fetched bytes are opaque and unverified, and execution occurs on every import unless a specific opt-out environment variable is set. Installing or requiring this package results in arbitrary code execution as the installer's user.

Malicious versions

1 flagged

35.7.4

Indicators of compromise (SHA-256)

626164264796294f1cb4322c03454ff5d9c50f7f0edb7534bfb6a5843d08079d

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

Campaign

IN-MAL-2026-015077

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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