Critical Malicious Code Vulnerability in rediff Package

rediff Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191416: Malicious code in rediff (npm). Affects rediff versions 1.0.5. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rediff package is an npm library that is commonly used for various functionalities in JavaScript applications. It is designed to facilitate specific tasks within the npm ecosystem. However, it has recently been identified as compromised, making it a significant security risk for developers and organizations utilizing this package.

Vulnerability Detail

The vulnerability stems from a malicious code injection attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other npm packages owned by the user. Additionally, it can establish persistence through GitHub actions and may even destroy the user's home directory. Any system running this package is considered fully compromised, necessitating immediate action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rediff

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, if you must continue using the rediff package temporarily, consider isolating your environment and ensuring that sensitive information is not accessible from the compromised system. However, this is not a long-term solution, and removal of the package is strongly recommended.

Conclusion

The rediff package has been compromised, leading to severe security implications for any systems using it. Immediate removal of the package and rotation of sensitive credentials is essential to mitigate risks. Continuous monitoring for vulnerabilities is recommended.

See every vulnerability recorded for rediff →

Share this vulnerability

FAQ

The rediff package is an npm library used in JavaScript applications for various functionalities. It has been compromised, posing a security risk.

The malicious code can steal sensitive tokens and credentials, propagate to other npm packages, and potentially destroy your home directory.

Immediately uninstall the rediff package and rotate any secrets or keys stored on the affected computer.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rediff

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback