devplatform-auth-clientnpm
devplatform-auth-client is a confirmed malicious npm package (MAL-2026-12698) that executes malicious code on install (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-auth-client (npm)
What this malware does
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.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-auth-client (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-auth-client across your stack and pipelines.
If you installed it — respond
Remove devplatform-auth-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If devplatform-auth-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-auth-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-auth-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.