devplatform-http-clientnpm
devplatform-http-client is a confirmed malicious npm package (MAL-2026-12712) that typosquats a legitimate package to trick installs (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-http-client (npm)
What this malware does
On require() of devplatform-http-client, index.js loads vendor.js which unconditionally invokes init(). The routine selects a platform-specific payload path and fetches a native binary from Cloudflare Workers subdomains whose hostnames are reconstructed from split string fragments (e.g. ["oob-worker.cf102-baf.workers.","de","v"].join("")). If the HTTPS fetch fails, it falls back to a DNS TXT covert channel against *.dl.wel1.ru: it resolves c.<domain> for a chunk count, batches TXT lookups against 0..N.<domain>, concatenates the responses, and base64-decodes them into an executable buffer. The fetched bytes are written to /tmp or %TEMP% under a disguised filename (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmodded 0755, and spawned detached via cmd.exe start /b or /bin/sh -c. The package is presented as an HTTP client wrapper, a purpose that requires no native-binary download and no DNS TXT smuggling; the destinations are anonymous infrastructure (workers.dev subdomains and an unrelated.ru domain), string-split to defeat static string scanning, and the dropped filenames impersonate telemetry/diagnostic tooling. Installing or loading this package yields remote code execution on the installer machine.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-http-client (version 35.8.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-http-client across your stack and pipelines.
If you installed it — respond
devplatform-http-client is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-http-client, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-http-client 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-http-client 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-http-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.