Which versions of rxnt-healthchecks-nestjs are malicious?

The following npm versions of rxnt-healthchecks-nestjs are flagged malicious: 1.0.2, 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate rxnt-healthchecks-nestjs if I installed it?

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

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

Yes — rxnt-healthchecks-nestjs is associated with the GHSA-c5h3-rjq7-c9pr, RLMA-2025-05144, RLUA-2025-05501, RLUA-2025-05939 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-healthchecks-nestjs 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-healthchecks-nestjs (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-healthchecks-nestjs across your stack and pipelines.

Malicious package

rxnt-healthchecks-nestjsnpm

rxnt-healthchecks-nestjs is a confirmed malicious npm package (MAL-2025-47346) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rxnt-healthchecks-nestjs (npm)

MAL-2025-47346

Immediate action

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

npm uninstall rxnt-healthchecks-nestjs

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.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

91466f0176011b114548780f79ecab9da3b995e89243c07548ea8be6e4a7b0d9

f7c371ecb4d3db3ed2bcfe0bc3bd34db00fb1a7357858ab2745876b150599573

a9a237e224ea7ac8071e7a33bfb1d13b6475e7c133f2ec232d255ae01d2d33e9

86df01a764b10205d3fd9e5d1dc9066bb1efcfcac2e0741ddea925658e833714

90ac6d3aed720bac56f2b133acca48fbdcf92a9aaa634d6b8fb8e8bd55530c7b

9329a57c7fa49142710f7586104a821272a7640f5d0c8034264eb30ea5cc2327

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

Campaign

GHSA-c5h3-rjq7-c9prRLMA-2025-05144RLUA-2025-05501RLUA-2025-05939

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rxnt-healthchecks-nestjs-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