Which versions of devplatform-po-transformer are malicious?

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

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

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

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

Yes — devplatform-po-transformer is associated with the IN-MAL-2026-015039 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-transformer 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-transformer (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-transformer across your stack and pipelines.

Malicious package

devplatform-po-transformernpm

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

Malicious code in devplatform-po-transformer (npm)

MAL-2026-12733

Immediate action

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

npm uninstall devplatform-po-transformer

What this malware does

On require of the package, platform.js detects OS/arch and downloads an opaque binary from Cloudflare Workers hostnames assembled at runtime from split-string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT covert-channel fallback under *.dl.wel1.ru that reassembles base64 chunks from N.<domain> TXT records. The fetched bytes are written to /tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows under deceptive filenames, chmod 0755, and spawned detached and unref'd via /bin/sh -c or cmd.exe /c start /b so the child survives the Node parent. There is no hash or signature verification; the download hosts are unrelated to the package publisher; a TTL marker at /tmp/.analytics_state suppresses re-execution within ~21000s. The fetch-decode-execute chain fires on import of the package's main entry, giving the operator of the remote endpoints arbitrary persistent code execution on the installer's host.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

555faac3cf4078b125af0858613813fb3f3bc780a573ddc5713b23d1046c9c71

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-po-transformer (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-transformer across your stack and pipelines.
If you installed it — respond
Remove devplatform-po-transformer 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-po-transformer 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-transformer 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-transformer 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-015039

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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