NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

devplatform-react-hooksnpm

Advisory published Updated

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
  1. Find it

    Search your lockfiles and build artifacts for devplatform-react-hooks (version 35.5.7).

  2. 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.

  3. Did it already run?

    If devplatform-react-hooks was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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.

Explore

devplatform-react-hooks (npm) malicious package — MAL-2026-12736 | O3 Security