Which versions of rxnt-authentication are malicious?

The following npm versions of rxnt-authentication are flagged malicious: 0.0.3, 0.0.4, 0.0.5, 0.0.6. Treat any of these as compromised.

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

rxnt-authentication 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-authentication — how do I know if it already compromised me?

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

Yes — rxnt-authentication is associated with the GHSA-2f8v-v92m-4q75, RLMA-2025-05143, RLUA-2025-05500, RLUA-2025-05938 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-authentication 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-authentication (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-authentication across your stack and pipelines.

Malicious package

rxnt-authenticationnpm

rxnt-authentication is a confirmed malicious npm package (MAL-2025-47345) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.3, 0.0.4, 0.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rxnt-authentication (npm)

MAL-2025-47345

Immediate action

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

npm uninstall rxnt-authentication

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

0.0.30.0.40.0.50.0.6

Indicators of compromise (SHA-256)

b91a5c1fc111834043bdb735e9a59a336ed170efa9b1396455c474bcd9752329

6fa451c907fde19135fec87b792eb4beed72ac8bedfe8ce892e1f47015d63861

16804f7208e8227ce92b0553e57f3eedd715cd5be01a1a8cf2986004ffea839c

a8ee2c9480830d3c54250f3cbb5898dc1b94a8ae11650b91eeafebc6d0ffe1a7

6067eea4bec78b1401099cd2da2ea88b638545a70a502c26d7d7568d888f5f15

46681a29b327c0b8d71234b63b967689abc5a46f8d5249422c0d88226d4a94db

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-authentication (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-authentication across your stack and pipelines.
If you installed it — respond
rxnt-authentication 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-authentication 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-authentication 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-authentication on npm has been identified as a malicious package (versions 0.0.3, 0.0.4, 0.0.5, 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2f8v-v92m-4q75RLMA-2025-05143RLUA-2025-05500RLUA-2025-05938

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rxnt-authentication-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