Which versions of rediff are malicious?

The following npm versions of rediff are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate rediff if I installed it?

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

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

Yes — rediff is associated with the GHSA-35xh-7xqf-84xp 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 rediff across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rediff (version 1.0.5).

Malicious package

rediffnpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

rediff is a confirmed malicious npm package (MAL-2025-191416) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rediff (npm)

MAL-2025-191416

Immediate action

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

npm uninstall rediff

What this malware does

The package rediff 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

9d50066b214c403cccc15801aeb0792a995e4789d973644869bb55e813d82a29

6f58213ac5761ffaaca614a73e2f1b9927e9f4b25f9dc8b3f64258411281ce41

c86aaca91ce5f75365f233d2d0448fcfe25ce792ebc203487993fdbed70e5c68

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rediff (version 1.0.5).
If you installed it — respond
rediff 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 rediff 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. rediff on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-35xh-7xqf-84xp

References

Credits

Amazon Inspector · finder

Detect & block this

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