devplatform-po-declaration-generatornpm
devplatform-po-declaration-generator is a confirmed malicious npm package (MAL-2026-12731) that executes malicious code on install (malicious version 35.2.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-po-declaration-generator (npm)
What this malware does
On require, index.js unconditionally loads init.js, which selects a platform-specific binary for linux/darwin/win32, downloads it from Cloudflare Workers hosts whose names are assembled by splitting and joining string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT fallback under sdk/ext/pkg/net subdomains of dl.wel1.ru, writes the bytes to /tmp or %TEMP% under disguised names such as dotnet_diag.exe and.cache_, chmods 0755, and detach-spawns the file via cp.spawn("/bin/sh", ["-c", path + " &"], {detached:true}) or cmd.exe /c start /b. No hash or signature verification is performed and the destinations are not documented publisher infrastructure. child_process is obtained via require("child_" + "process") to evade static matching. lib/telemetry.js ships an 81 KB second loader that reproduces the same fetch, base64-decode, chmod 0755, and /bin/sh -c spawn chain. The package's declared purpose (PO declaration generator) does not require fetching and executing native binaries from anonymous Cloudflare Workers hosts.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-po-declaration-generator (version 35.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-po-declaration-generator across your stack and pipelines.
If you installed it — respond
Remove devplatform-po-declaration-generator 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-declaration-generator 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-declaration-generator 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks devplatform-po-declaration-generator-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.