What does the devplatform-utils malware do?

devplatform-utils@35.5.2 ships an index.js whose main module require()s _bootstrap.js, which on load downloads a platform-specific binary payload from string-split-obfuscated Cloudflare Workers endpoints (e.g. oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback via *.dl.wel1.ru. The payload is written to /var/tmp/.cache_ on Unix or %TEMP%\dotnet_diag_ .exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c ' &' or cmd.exe /c start /b. Destination hostnames are assembled at runtime by.join('') on fragmented string arrays (_NODES, _DNS_MAP) to evade static string scans, and the dropped file is given cover-story names (dotnet_diag_*,.cache_*,.analytics_state). A

Which versions of devplatform-utils are malicious?

The following npm versions of devplatform-utils are flagged malicious: 35.5.2. Treat any of these as compromised.

How do I remediate devplatform-utils if I installed it?

devplatform-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If devplatform-utils 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-utils part of a known attack campaign?

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

Malicious package

devplatform-utilsnpm

devplatform-utils is a confirmed malicious npm package (MAL-2026-13271) that steals credentials and exfiltrates sensitive data (malicious version 35.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-utils (npm)

MAL-2026-13271

Immediate action

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

npm uninstall devplatform-utils

What this malware does

[email protected] ships an index.js whose main module require()s bootstrap.js, which on load downloads a platform-specific binary payload from string-split-obfuscated Cloudflare Workers endpoints (e.g. oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback via *.dl.wel1.ru. The payload is written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. Destination hostnames are assembled at runtime by.join('') on fragmented string arrays (NODES, DNS_MAP) to evade static string scans, and the dropped file is given cover-story names (dotnet_diag*,.cache*,.analytics_state). A rate-limit token stored at /tmp/.analytics_state (EXPIRE_SEC=21227, ~5.9 hours) causes the remote binary to be re-fetched and re-executed on subsequent require() calls, providing a persistent operator-controlled code-delivery channel. Environment variables DISABLE_TELEMETRY / DO_NOT_TRACK are checked as a cover story consistent with a legitimate telemetry opt-out. No hash or signature verification is performed on the fetched binary.

Malicious versions

1 flagged

35.5.2

Indicators of compromise (SHA-256)

0244bc7396ea5f52d909130a7d685fee98c0dda29cb18b82d17e8c9c90dff552

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-utils (version 35.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-utils across your stack and pipelines.
If you installed it — respond
devplatform-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If devplatform-utils 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-utils 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-utils on npm has been identified as a malicious package (version 35.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015723

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database