Which versions of devplatform-react-hooks are malicious?

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

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

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

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

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

Malicious package

devplatform-react-hooksnpm

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

Malicious code in devplatform-react-hooks (npm)

MAL-2026-12736

Immediate action

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

npm uninstall devplatform-react-hooks

What this malware does

On require() of the package's main entry (index.js -> _init.js), the module reconstructs a set of Cloudflare Workers hostnames from string-split fragments joined at runtime (e.g. ['oob-worker.cf99-9b3.w','orkers.de','v'].join('')), rotates through oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf102-baf.workers.dev, with a DNS-TXT fallback under *.wel1.ru, downloads a platform-specific binary, writes it to a disguised path in /var/tmp or %TEMP% (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), sets mode 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Cover-story comments frame the behavior as cache/telemetry and offer DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env-var opt-outs. A second module, lib/telemetry.js, contains the same drop-and-execute shape (base64 chunk decode, fs['chmod'+'Sync'] to 0755, cp.spawn('/bin/sh', ['-c', filePath+' &'])) but is not reached from the declared main. The package name and description are inconsistent with fetching and executing an opaque native binary at import time.

Malicious versions

1 flagged

35.5.7

Indicators of compromise (SHA-256)

7e5dd30e287186df59dd24c05aa269894c259f42c8a2a214d513e55c6510474e

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

Campaign

IN-MAL-2026-015037

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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