Which versions of rhynpm are malicious?

The following npm versions of rhynpm are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate rhynpm if I installed it?

Remove rhynpm 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.

I already installed rhynpm — how do I know if it already compromised me?

If rhynpm was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is rhynpm part of a known attack campaign?

Yes — rhynpm is associated with the RLMA-2025-04670, RLUA-2026-06454 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 rhynpm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rhynpm (5 malicious versions).

Malicious package

rhynpmnpm

Advisory published Aug 14, 2025Updated Sep 1, 2026

rhynpm is a confirmed malicious npm package (MAL-2025-32206) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rhynpm (npm)

MAL-2025-32206

Immediate action

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

npm uninstall rhynpm

What this malware does

The package rhynpm was found to contain malicious code.

Malicious versions

5 flagged

1.0.01.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

da25c3c579bc2c0b09f42da60ce04f054b1f7b25b401282f1ca9b3a0d44d5d21

76dafd436ad28f36ce511eb7274b9ab2b273c9c31e555aced7ae08ad74105c27

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rhynpm (5 malicious versions).
If you installed it — respond
Remove rhynpm 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.
Did it already run?
If rhynpm was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rhynpm on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04670RLUA-2026-06454

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rhynpm-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