Which versions of devplatform-hooks are malicious?

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

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

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

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

Yes — devplatform-hooks is associated with the IN-MAL-2026-015067 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-hooks 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-hooks (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-hooks across your stack and pipelines.

Malicious package

devplatform-hooksnpm

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

Malicious code in devplatform-hooks (npm)

MAL-2026-12711

Immediate action

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

npm uninstall devplatform-hooks

What this malware does

On require() of devplatform-hooks, index.js loads init.js, which selects a platform-specific payload URL and fetches an executable from obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev). The destination hostnames are assembled at runtime from split string fragments joined together to evade static inspection. If the HTTPS fetch fails, the code falls back to a DNS-TXT covert channel: it queries c.<domain> under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru for a chunk count, iteratively resolves N.<domain> TXT records, concatenates and base64-decodes the responses into a binary. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, then executed detached via cp.spawn("/bin/sh", ["-c", path+" &"], {detached:true}) or the Windows equivalent. The package name, the obfuscation of destinations, the DNS-TXT covert transport, the disguised drop paths, and the detached execution together constitute a remote code execution dropper triggered on any install or import of this package.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

03e653399f20fec2b4b40c7c8921090939a1205110d866d23e4b605802cbc75d

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-hooks (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-hooks across your stack and pipelines.
If you installed it — respond
Remove devplatform-hooks 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-hooks 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-hooks 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-hooks 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-015067

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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