Which versions of devplatform-iam-client are malicious?

The following npm versions of devplatform-iam-client are flagged malicious: 35.5.6. Treat any of these as compromised.

How do I remediate devplatform-iam-client if I installed it?

Remove devplatform-iam-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.

I already installed devplatform-iam-client — how do I know if it already compromised me?

If devplatform-iam-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.

Is devplatform-iam-client part of a known attack campaign?

Yes — devplatform-iam-client is associated with the IN-MAL-2026-015056 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-iam-client 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-iam-client (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-iam-client across your stack and pipelines.

Malicious package

devplatform-iam-clientnpm

devplatform-iam-client is a confirmed malicious npm package (MAL-2026-12715) that executes malicious code on install (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-iam-client (npm)

MAL-2026-12715

Immediate action

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

npm uninstall devplatform-iam-client

What this malware does

The package presents a no-op DevplatformIamClient export, but index.js unconditionally require()s./init.js on load. init.js selects a platform-specific path, reconstructs Cloudflare Workers endpoints from split string arrays (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) and a DNS-TXT covert-channel fallback under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru (base64 chunks reassembled from TXT records), downloads an opaque binary, writes it to a disguised path (/tmp/.cache<hex> or %TEMP%/dotnet_diag<hex>.exe), chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd. No hash or signature verification is performed. Endpoint hostnames are assembled at runtime via array-join to evade static extraction, and the staged file names ('.analytics_state', 'dotnet_diag_*.exe') act as cover. The package name, 'Internal devplatform iam client module' description, empty dependencies, and stub main are consistent with a dependency-confusion lure against an internal registry name; the harm is full-host code execution on the installer at require() time.

Malicious versions

1 flagged

35.5.6

Indicators of compromise (SHA-256)

494d7de346ffd38cb213791a60c0a1e19d6391e79643e052d31c8ac1e8028b3f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-iam-client (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-iam-client across your stack and pipelines.
If you installed it — respond
Remove devplatform-iam-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-iam-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-iam-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

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

Campaign

IN-MAL-2026-015056

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-iam-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database