Which versions of devplatform-po-loader are malicious?

The following npm versions of devplatform-po-loader are flagged malicious: 35.1.8. Treat any of these as compromised.

How do I remediate devplatform-po-loader if I installed it?

devplatform-po-loader is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-po-loader, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed devplatform-po-loader — how do I know if it already compromised me?

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

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

Malicious package

devplatform-po-loadernpm

devplatform-po-loader is a confirmed malicious npm package (MAL-2026-12732) that typosquats a legitimate package to trick installs (malicious version 35.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-po-loader (npm)

MAL-2026-12732

Immediate action

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

npm uninstall devplatform-po-loader

What this malware does

On require(), the package loads platform.js which selects a platform-specific path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads a binary over HTTPS from obfuscated Cloudflare Workers endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to /tmp or %TEMP% under disguised names (dotnet_diag<tag>.exe on Windows,.cache_<tag> on Unix impersonating Microsoft dotnet-diag), chmods 0755, and spawns it detached via /bin/sh or cmd. Host names are reconstructed at runtime through split-string join to evade static analysis, and a fallback covert channel resolves TXT records under *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reading a chunk count from c.<domain> and base64-decoding chunks from <i>.<domain> TXT records to reassemble and execute the payload. A marker file named.analytics_state and a 'Skip in CI environments' comment further disguise intent. The package advertises itself as a trivial loader library; the shipped code contains no library functionality — only the dropper.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

185d53460e4ec6534c0b4c8f3de1c0eb2d0134eaf161d8e0211a46bca273ad69

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-po-loader (version 35.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-po-loader across your stack and pipelines.
If you installed it — respond
devplatform-po-loader is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-po-loader, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-po-loader 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-po-loader 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-po-loader on npm has been identified as a malicious package (version 35.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015047

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-po-loader-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