Which versions of devplatform-di are malicious?

The following npm versions of devplatform-di are flagged malicious: 35.5.5. Treat any of these as compromised.

How do I remediate devplatform-di if I installed it?

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

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

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

Malicious package

devplatform-dinpm

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

Malicious code in devplatform-di (npm)

MAL-2026-12709

Immediate action

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

npm uninstall devplatform-di

What this malware does

On require('devplatform-di'), index.js loads compat.js which fetches a platform-specific executable from string-split-obfuscated hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), with a base64-chunk DNS TXT fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /tmp or %TEMP% under cover-story filenames such as dotnet_diag<rnd>.exe and.cache_<rnd>, chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames and sensitive API names (child_process, chmodSync) are assembled from split fragments at runtime to evade static search. lib/telemetry.js contains the same shape (require("child_"+"process"), base64-decoded buffer, spawn /bin/sh, chmodSync 0755). The package presents itself as a trivial dependency-injection stub, unrelated to any legitimate native-binary requirement.

Malicious versions

1 flagged

35.5.5

Indicators of compromise (SHA-256)

e3fd866e9abd20e9fa0c9ca40131d13b1ca98e2abbe73f53fd063581a65256d9

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

Campaign

IN-MAL-2026-015066

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-di-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