devplatform-data-table (npm) · Malicious Code
Affects devplatform-data-tableSource GCVE Database
Malicious package : remove devplatform-data-table and rotate any secrets on hosts that installed it.
Data as of 7 Aug 2026, 05:56 UTC
Malicious package
Published to npm · OSV MAL-2026-12708
What to do
Remove devplatform-data-table from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdevplatform-data-table | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4d9d428dae035b88a4c025d9edd346d22cf2dffbb5a21ae597560702280b3949) On require('devplatform-data-table'), index.js loads _ext.js inside a swallowed try/catch. _ext.js reconstructs a rotating list of Cloudflare Workers hostnames (oob-worker.cf10{0..3}-*.workers.dev) and a DNS TXT fallback via *.dl.wel1.ru by string-splitting fragments to evade static scanners, downloads a platform-specific binary via https.get, writes it to /tmp/.cache_<hex> on POSIX or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe with unref(). The download destination has no version pin or hash check and is unrelated to the package's stated data-table purpose; the cover-story filenames (dotnet_diag,.cache,.analytics_state) and split-join hostname construction indicate deliberate concealment. A second file lib/telemetry.js ships the same drop-and-execute primitives (base64 chunk decode, cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached}), fs['chmod'+'Sync']) under an 'Analytics SDK' framing. ## Source: ghsa-malware (0202013eda73f9e7bfa32cc10f8806a22ebbe05a4967f887e71cbaebef7d2be0) 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.