devplatform-api-v1-endpointnpm
devplatform-api-v1-endpoint is a confirmed malicious npm package (MAL-2026-12693) that opens a backdoor for remote access (malicious version 35.9.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-api-v1-endpoint (npm)
What this malware does
On require, adapter.js selects a platform-specific asset path and fetches an executable from string-split-obfuscated hosts under oob-worker.cf10*-*.workers.dev, falling back to base64-encoded payload chunks reassembled from DNS TXT queries against *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched bytes are written to /var/tmp or %TEMP% under cover-story filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b, with no hash or signature verification. A persistence marker (.analytics_state) with a ~6.4h freshness window throttles repeat activity. The delivery mechanism has no relation to the package's advertised SDK purpose, and the C2 host strings are reconstructed at runtime from split fragments via.join('') to defeat static analysis.
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-api-v1-endpoint (version 35.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-api-v1-endpoint across your stack and pipelines.
If you installed it — respond
devplatform-api-v1-endpoint 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-api-v1-endpoint 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-api-v1-endpoint 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-api-v1-endpoint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.