Which versions of devplatform-react-query-clients are malicious?

The following npm versions of devplatform-react-query-clients are flagged malicious: 35.7.7. Treat any of these as compromised.

How do I remediate devplatform-react-query-clients if I installed it?

devplatform-react-query-clients is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-react-query-clients, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed devplatform-react-query-clients — how do I know if it already compromised me?

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

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

Malicious package

devplatform-react-query-clientsnpm

devplatform-react-query-clients is a confirmed malicious npm package (MAL-2026-12738) that typosquats a legitimate package to trick installs (malicious version 35.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-react-query-clients (npm)

MAL-2026-12738

Immediate action

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

npm uninstall devplatform-react-query-clients

What this malware does

On require() of the package, index.js loads adapter.js which downloads a platform-specific binary from hardcoded Cloudflare workers.dev endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched binary is written to /var/tmp or %TEMP% with a randomized dot-prefixed name (e.g. dotnet_diag<hex>.exe,.cache_<hex>), chmod'd 0755, and spawned detached via /bin/sh -c or cmd /c start. Host strings and API names are obfuscated via split/join concatenation (e.g. ["oob-worker.cf99-9b3.workers.d","ev"].join(""), fs["chmod"+"Sync"], require("child_"+"process")) to evade static scanners. The dropper is disguised as an analytics/telemetry module with cover-story filenames (.analytics_state, dotnet_diag_* impersonating a Microsoft diagnostic tool) and env-variable opt-out gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK). lib/telemetry.js (81 KB) mirrors the same fetch/chmod/spawn pattern under an apm.node label. Fetching and executing unpinned, unauthenticated binaries from anonymous Cloudflare Workers subdomains at library import yields full-host remote code execution on any environment that installs or imports this package.

Malicious versions

1 flagged

35.7.7

Indicators of compromise (SHA-256)

192681d10673d935bcba617102ed5581cc928ba8ebedda203cebe5d33d7f067a

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-react-query-clients (version 35.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-react-query-clients across your stack and pipelines.
If you installed it — respond
devplatform-react-query-clients is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-react-query-clients, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-react-query-clients 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-query-clients 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-query-clients on npm has been identified as a malicious package (version 35.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015038

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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