Which versions of rediff-viewer are malicious?

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

How do I remediate rediff-viewer if I installed it?

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

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

Yes — rediff-viewer is associated with the GHSA-gw6x-9h9w-2rjg 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-viewer 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 rediff-viewer (version 0.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rediff-viewer across your stack and pipelines.

Malicious package

rediff-viewernpm

Malicious code in rediff-viewer (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191417

Immediate action

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

npm uninstall rediff-viewer

What this malware does

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

0.0.7

Indicators of compromise (SHA-256)

8ba11a9dfe49eb38649ff739a9d5a1123c127ff06f780ee7cd804f259d680a8d

3d19e3e0f8fc94b15fad4cfc7a82c6f22f66e111e2ba3c5ce2eaf4acc69e288d

2b40d95d5fff90452e9bba5b17b0ddb9c3842ffcb276e9418428a9b969f60129

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 rediff-viewer (version 0.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rediff-viewer across your stack and pipelines.
If you installed it — respond
rediff-viewer 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-viewer 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 rediff-viewer 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. rediff-viewer on npm has been identified as a malicious package (version 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gw6x-9h9w-2rjg

References

Credits

Amazon Inspector · finder

Detect & block this

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