Which versions of devplatform-supafetch are malicious?

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

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

devplatform-supafetch 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-supafetch — how do I know if it already compromised me?

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

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

Malicious package

devplatform-supafetchnpm

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

Malicious code in devplatform-supafetch (npm)

MAL-2026-13265

Immediate action

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

npm uninstall devplatform-supafetch

What this malware does

[email protected] is advertised as a fetch helper but on require() drops and executes an opaque native binary. index.js unconditionally loads./ext.js, which selects a platform-specific payload path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads it from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf100-.workers.dev through cf103-.workers.dev), with a DNS-TXT fallback channel over subdomains of *.dl.wel1.ru that reassembles a base64-encoded payload from split TXT records. The downloaded bytes are written to /tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmod 0755, and launched detached via spawn("/bin/sh", ["-c", fp+" &"]).unref() (or the cmd equivalent on Windows). Host names and DNS-fallback domain segments are constructed via ["...","..."].join("") to defeat static string matching. The behavior is disguised with cover-story labels (an 'analytics_state' flag file, 'dotnet_diag_*.exe' filename, gating on DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env vars) that make the dropper appear to be optional telemetry. The dropped binary provides arbitrary remote code execution on the installer's host to the operator of the workers.dev / wel1.ru infrastructure.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

8dc92f63aa9d199fde2a42c1298a9c620b5823b5252d16c9450456e5efbb154d

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-supafetch (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-supafetch across your stack and pipelines.
If you installed it — respond
devplatform-supafetch 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-supafetch 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-supafetch 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-supafetch on npm has been identified as a malicious package (version 35.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015727

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-supafetch-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