devplatform-auth-client (npm) · Malicious Code
Affects devplatform-auth-clientSource GCVE Database
Malicious package : remove devplatform-auth-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-12698
What to do
Remove devplatform-auth-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-auth-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 (3b5d92af4e479fded008aa25786634ef3869a37c3624f612a320d308808a0626) Requiring devplatform-auth-client loads `_bootstrap.js`, which selects a platform-specific payload URL, downloads opaque bytes over HTTPS from hardcoded Cloudflare `workers.dev` subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-based fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, writes them to /tmp or %TEMP% under decoy names such as `.cache_<hex>` and `dotnet_diag_<hex>.exe`, chmods 0755, and spawns them detached via `/bin/sh -c` or `cmd`. The destination hostnames and dangerous API names are assembled from split-string fragments joined at runtime to evade static scanners. A sibling `lib/telemetry.js` module, presented as an analytics SDK, contains a parallel loader that base64-decodes a payload, dynamically resolves `chmodSync`, and spawns the decoded file. The fetched bytes are unpinned, unverified, and unrelated to any documented publisher. ## Source: ghsa-malware (84dec7cc75aa19ce40a478689c787d0a170d2f8f52aea764f4357e1b83e496a0) 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.