Which versions of rxnt-kue are malicious?

The following npm versions of rxnt-kue are flagged malicious: 1.0.4, 1.0.5, 1.0.6, 1.0.7. Treat any of these as compromised.

How do I remediate rxnt-kue if I installed it?

rxnt-kue is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed rxnt-kue — how do I know if it already compromised me?

If rxnt-kue 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 rxnt-kue part of a known attack campaign?

Yes — rxnt-kue is associated with the GHSA-gww9-289f-x73q, RLMA-2025-05145, RLUA-2025-05502, RLUA-2025-05940 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 rxnt-kue 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 rxnt-kue (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rxnt-kue across your stack and pipelines.

Malicious package

rxnt-kuenpm

rxnt-kue is a confirmed malicious npm package (MAL-2025-47347) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.4, 1.0.5, 1.0.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rxnt-kue (npm)

MAL-2025-47347

Immediate action

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

npm uninstall rxnt-kue

What this malware does

The package was compromised and malicious code added.

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

4 flagged

1.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

4ec749849185c3ae0212a13b39a44ff783ea47aa560116e7af14df511632585e

85771d4d8299171e928352772dcd23901e89767cd4b22a3f95a922e507468537

c7bd82738d6c453b79c344b57666c78ebb2311efe344b4c44aba4beae7ea2d9d

6708dc925f074f6aec9348fe7067e678d01f873bd053ba7c82abbb6a0f4fabc7

88198936f4a1ce85f2ccad19b5e774518647a14f5b2e0fed61efbc086bac8f4e

e0243f3743edb55d4318700513531fa85f43c18ebec76e3b9dab41778a28c80a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rxnt-kue (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rxnt-kue across your stack and pipelines.
If you installed it — respond
rxnt-kue is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rxnt-kue 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 rxnt-kue 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. rxnt-kue on npm has been identified as a malicious package (versions 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gww9-289f-x73qRLMA-2025-05145RLUA-2025-05502RLUA-2025-05940

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rxnt-kue-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database