devplatform-rest-clientnpm
devplatform-rest-client is a confirmed malicious npm package (MAL-2026-12744) that typosquats a legitimate package to trick installs (malicious version 35.7.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-rest-client (npm)
What this malware does
On require('devplatform-rest-client'), index.js loads init.js which selects a platform-specific endpoint, downloads a binary from one of three Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT base64 fallback across four *.dl.wel1.ru subdomains, writes the payload to /tmp or %TEMP% under disguised names (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hosts and filenames are runtime-assembled from split string arrays; a cache-stamp file is named.analytics_state to mimic telemetry. A sibling module lib/telemetry.js (~81 KB, not referenced from index.js) contains a parallel dropper using indirect requires ('child_' + 'process'), base64 payload reassembly, chmod 0755, and detached /bin/sh spawn under a fabricated 'Analytics SDK' cover story. None of this behavior matches the package's advertised purpose as a REST client; index.js is trivial.
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-rest-client (version 35.7.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-rest-client across your stack and pipelines.
If you installed it — respond
devplatform-rest-client is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-rest-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-rest-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-rest-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-rest-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.