Which versions of devplatform-data-table are malicious?

The following npm versions of devplatform-data-table are flagged malicious: 35.4.1. Treat any of these as compromised.

How do I remediate devplatform-data-table if I installed it?

Remove devplatform-data-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.

I already installed devplatform-data-table — how do I know if it already compromised me?

If devplatform-data-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.

Is devplatform-data-table part of a known attack campaign?

Yes — devplatform-data-table is associated with the IN-MAL-2026-015068 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-data-table 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-data-table (version 35.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-data-table across your stack and pipelines.

Malicious package

devplatform-data-tablenpm

devplatform-data-table is a confirmed malicious npm package (MAL-2026-12708) that executes malicious code on install (malicious version 35.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-data-table (npm)

MAL-2026-12708

Immediate action

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

npm uninstall devplatform-data-table

What this malware does

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.

Malicious versions

1 flagged

35.4.1

Indicators of compromise (SHA-256)

4d9d428dae035b88a4c025d9edd346d22cf2dffbb5a21ae597560702280b3949

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-data-table (version 35.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-data-table across your stack and pipelines.
If you installed it — respond
Remove devplatform-data-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-data-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-data-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

No. devplatform-data-table on npm has been identified as a malicious package (version 35.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015068

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-data-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database