Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @sev-ui-verse published 22 malicious packages. See the full campaign →
Malicious package

@sev-ui-verse/react-query-clientnpm

@sev-ui-verse/react-query-client is a confirmed malicious npm package (MAL-2025-47544) that executes malicious code on install (malicious version 339.52.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sev-ui-verse/react-query-client (npm)

MAL-2025-47544
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sev-ui-verse/react-query-client

What this malware does

The package @sev-ui-verse/react-query-client was found to contain malicious code.

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

1 flagged
339.52.1

Indicators of compromise (SHA-256)

665474d528ec1e43349cea649e53f67e00e56ef1f98b376e17c5a672fa0a7270
4c3519c72cea3be641b86aa966fe42256e6a685bb86ae581cb9669292cea08b9
c3fe8e95e99bcb6bf093f700ae5dd340abce2d1bd087b60142f6355c77f12cc9

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sev-ui-verse/react-query-client (version 339.52.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sev-ui-verse/react-query-client across your stack and pipelines.

  2. If you installed it — respond

    Remove @sev-ui-verse/react-query-client 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 @sev-ui-verse/react-query-client 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.

  4. How O3 protects you

    O3 blocks @sev-ui-verse/react-query-client 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. @sev-ui-verse/react-query-client on npm has been identified as a malicious package (version 339.52.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p4fr-2h4g-xwcrRLMA-2025-04895RLUA-2025-05258

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @sev-ui-verse/react-query-client-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

@sev-ui-verse/react-query-client (npm) malicious package — MAL-2025-47544 | O3 Security