devplatform-cli-plugin-testnpm
devplatform-cli-plugin-test is a confirmed malicious npm package (MAL-2026-12703) that opens a backdoor for remote access (malicious version 35.4.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-cli-plugin-test (npm)
What this malware does
On require(), runtime.js selects a platform-specific asset, downloads a binary over https.get from hardcoded Cloudflare Workers hosts (with a DNS TXT base64 fallback under dl.wel1.ru), writes it to /var/tmp or %TEMP% under names mimicking diagnostic tools (dotnet_diag.exe,.cache_,.analytics_state), chmods it 0o755, and spawns it detached via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or cmd.exe /c start /b. C2 hostnames and fallback domains are reconstructed at runtime from split-string arrays to evade static scanners. No hash or signature verification. The destinations are non-publisher, mutable, and disguised, and the package advertises itself as test fixtures while performing this drop-and-execute on load.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-cli-plugin-test (version 35.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-cli-plugin-test across your stack and pipelines.
If you installed it — respond
devplatform-cli-plugin-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-cli-plugin-test 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-plugin-test 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks devplatform-cli-plugin-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.