hubert-react-querynpm
hubert-react-query is a confirmed malicious npm package (MAL-2026-12181) that executes malicious code on install (malicious version 20.6.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hubert-react-query (npm)
What this malware does
The package's main entry (index.js) unconditionally requires./setup.js on import. setup.js reconstructs Cloudflare Workers hostnames from string-fragment arrays at runtime (e.g. ["oob-worker.cf103-070",".workers",".dev"].join("")) targeting oob-worker.cf103-070.workers.dev, cf102-baf.workers.dev, cf99-9b3.workers.dev, and cf100-416.workers.dev, with a DNS-TXT base64 fallback channel over resolvers under *.dl.well1.site. It downloads a platform-specific native binary via https.get, writes it to /var/tmp/.cache_<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows to disguise the file, chmods it 0755, and spawns it detached via /bin/sh -c or cmd, then unref()s the child so it survives the parent. Cover-story comments ('Shuffle endpoints', 'analytics_state', a DISABLE_TELEMETRY opt-out) frame the dropper as telemetry. The destinations are attacker-controlled workers.dev/DDNS hosts, the delivered content is an opaque compiled binary unrelated to the package's advertised react-query purpose, and execution occurs on plain require() of the module.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hubert-react-query (version 20.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubert-react-query across your stack and pipelines.
If you installed it — respond
Remove hubert-react-query 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 hubert-react-query 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 hubert-react-query 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks hubert-react-query-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.