platform-ui-codemodsnpm
platform-ui-codemods is a confirmed malicious npm package (MAL-2026-12041) that executes malicious code on install (malicious version 20.6.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in platform-ui-codemods (npm)
What this malware does
On require() of the package, index.js loads./compat.js whose top-level init() downloads a platform-specific binary from a set of Cloudflare Workers mirrors whose hostnames are assembled at runtime from split-string arrays joined with.join("") (e.g. oob-worker.cf1*.workers.dev), with a DNS-TXT covert-channel fallback that reconstructs a base64 payload from chunked TXT records under c.<domain>/<n>.<domain> at *.dl.well1.site (tin/tina/ldr/win subdomains). The fetched bytes are written to a hidden/decoy path ("/tmp/.cache<hex>" on Unix, "%TEMP%\dotnet_diag_<hex>.exe" on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe with a cooldown stamp file (".analytics_state") to avoid re-execution. Hostname obfuscation, decoy filenames, DNS-TXT egress fallback, and detached execution collectively indicate a staged remote-code-execution dropper that fires automatically on install/require of this package.
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 platform-ui-codemods (version 20.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging platform-ui-codemods across your stack and pipelines.
If you installed it — respond
Remove platform-ui-codemods 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 platform-ui-codemods 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 platform-ui-codemods 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 platform-ui-codemods-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.