Which versions of devplatform-api-clients are malicious?

The following npm versions of devplatform-api-clients are flagged malicious: 35.6.8. Treat any of these as compromised.

How do I remediate devplatform-api-clients if I installed it?

devplatform-api-clients is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed devplatform-api-clients — how do I know if it already compromised me?

If devplatform-api-clients 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.

Is devplatform-api-clients part of a known attack campaign?

Yes — devplatform-api-clients is associated with the IN-MAL-2026-015078 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find devplatform-api-clients across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-api-clients (version 35.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-api-clients across your stack and pipelines.

Malicious package

devplatform-api-clientsnpm

devplatform-api-clients is a confirmed malicious npm package (MAL-2026-12691) that steals credentials and exfiltrates sensitive data (malicious version 35.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-api-clients (npm)

MAL-2026-12691

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall devplatform-api-clients

What this malware does

index.js unconditionally requires./setup.js, which on module load fetches a platform-specific binary from one of three Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev), with a DNS TXT-record fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The endpoints are concealed by splitting the hostnames into string arrays that are joined at runtime. The downloaded binary is written to /tmp or %TEMP% under stealth names such as dotnet_diag_<rand>.exe or.cache_<rand> (setup.js line ~119), chmod 0755'd, and spawned detached via spawn('/bin/sh', ['-c', fp+' &']).unref() or the cmd equivalent. A marker file gates re-execution and DISABLE_TELEMETRY / DO_NOT_TRACK env vars are honored as a plausible-deniability cover. The package advertises itself as a service-client SDK; a client SDK has no need to fetch and execute an opaque native binary from a third-party edge host at require time.

Malicious versions

1 flagged

35.6.8

Indicators of compromise (SHA-256)

e548a0e6be161acd612b2729edd26e431f1bc4405e625daf957ede88db94e017

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-api-clients (version 35.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-api-clients across your stack and pipelines.
If you installed it — respond
devplatform-api-clients is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If devplatform-api-clients 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-api-clients 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

No. devplatform-api-clients on npm has been identified as a malicious package (version 35.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015078

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-api-clients-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database