devplatform-tablenpm
devplatform-table is a confirmed malicious npm package (MAL-2026-13266) that executes malicious code on install (malicious version 35.7.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-table (npm)
What this malware does
On require() of devplatform-table, index.js loads./compat which selects a platform-specific payload path, downloads an executable from string-concatenation-obfuscated Cloudflare Workers hosts (reconstructed from fragments such as ["oob-worker.cf103-070.workers.d","ev"].join("")) with a DNS-TXT fallback via *.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Sensitive API identifiers including 'child_process' and 'chmodSync' are also reassembled at runtime from fragments to evade static analysis. The fetched binary is unpinned, unverified, and comes from anonymous worker hosts unrelated to any package publisher domain, giving whoever controls those hosts arbitrary code execution on any machine that installs or imports this package.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-table (version 35.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-table across your stack and pipelines.
If you installed it — respond
Remove devplatform-table 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-table 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-table 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-table-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.