Critical Malicious Code Vulnerability in nextjs-package-purify
Summary
MAL-2025-5939: Malicious code in nextjs-package-purify (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
nextjs-package-purify is an npm package designed to enhance the functionality of Next.js applications by providing utilities for code purification. However, it has been identified to contain embedded malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the nextjs-package-purify package. This code can lead to full system compromise, allowing attackers to gain unauthorized access to sensitive information, including secrets and keys stored on the affected machine. The malicious nature of the code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system with this package installed as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nextjs-package-purifyIf 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
Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package entirely. It is essential to monitor your systems for any signs of compromise after removal.
Conclusion
The nextjs-package-purify package contains malicious code that poses a severe security risk. Users must remove the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for nextjs-package-purify →
FAQ
Immediately remove the package from your project and rotate any sensitive information stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.
As of now, there is no patched version available. The best course of action is to remove the package entirely.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest versions.
