What does the devplatform-cli-contracts malware do?

On require() of the package, index.js loads _compat.js which reconstructs destination hostnames from split string arrays (e.g. ["oob-worker.cf100-416.worker","s.","dev"].join("") and DNS-TXT fallbacks assembled from ['sd','k.dl.wel1.','ru']), fetches a platform-specific binary via HTTPS, writes it to /tmp or %TEMP% under decoy names such as dotnet_diag_ .exe and.cache_ , chmods 0755, and spawns it detached via cp.spawn("/bin/sh",["-c", fp+" &"],{detached:true}).unref(). A cooldown marker (.analytics_state) suppresses repeat execution. The destinations are not publisher-owned infrastructure, the fetched bytes are unverified, and the fetch-and-exec chain fires automatically on import.

Which versions of devplatform-cli-contracts are malicious?

The following npm versions of devplatform-cli-contracts are flagged malicious: 35.7.3. Treat any of these as compromised.

How do I remediate devplatform-cli-contracts if I installed it?

Remove devplatform-cli-contracts 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-cli-contracts — how do I know if it already compromised me?

If devplatform-cli-contracts 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-cli-contracts part of a known attack campaign?

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

Malicious package

devplatform-cli-contractsnpm

devplatform-cli-contracts is a confirmed malicious npm package (MAL-2026-12700) that executes malicious code on install (malicious version 35.7.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-cli-contracts (npm)

MAL-2026-12700

Immediate action

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

npm uninstall devplatform-cli-contracts

What this malware does

On require() of the package, index.js loads compat.js which reconstructs destination hostnames from split string arrays (e.g. ["oob-worker.cf100-416.worker","s.","dev"].join("") and DNS-TXT fallbacks assembled from ['sd','k.dl.wel1.','ru']), fetches a platform-specific binary via HTTPS, writes it to /tmp or %TEMP% under decoy names such as dotnet_diag<hex>.exe and.cache_<hex>, chmods 0755, and spawns it detached via cp.spawn("/bin/sh",["-c", fp+" &"],{detached:true}).unref(). A cooldown marker (.analytics_state) suppresses repeat execution. The destinations are not publisher-owned infrastructure, the fetched bytes are unverified, and the fetch-and-exec chain fires automatically on import.

Malicious versions

1 flagged

35.7.3

Indicators of compromise (SHA-256)

6bc9fcdf16d7e6c67e3dbc20a6e8bdec551687bc20fffa3c434a35ca387ffade

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-cli-contracts (version 35.7.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-cli-contracts across your stack and pipelines.
If you installed it — respond
Remove devplatform-cli-contracts 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-cli-contracts 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-cli-contracts 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-cli-contracts on npm has been identified as a malicious package (version 35.7.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015072

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-cli-contracts-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