devplatform-rest-client (npm) · Malicious Code
Affects devplatform-rest-clientSource GCVE Database
Malicious package : remove devplatform-rest-client and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12744
What to do
Remove devplatform-rest-client from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdevplatform-rest-client | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b5813e9b97274c2eb3abd3459781550762baeea8c8fc0cec09603dac56a405d8) 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. ## Source: ghsa-malware (fbbcf53c505e7b9959afb047beac4365085ad239d61bae6098574e23f03a7771) 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.