Critical Malicious Code Vulnerability in next-preconfig Package
Summary
MAL-2025-6365: Malicious code in next-preconfig (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
The next-preconfig package is an npm library designed to streamline configuration for Next.js applications. It provides developers with tools to manage settings and environment variables efficiently. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability stems from embedded malicious code within the next-preconfig package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there is no guarantee that all traces of the malware will be eliminated, leaving systems vulnerable to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall next-preconfigIf 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 temporary measure, you can isolate the affected application from the internet and restrict access to sensitive data until the package is removed and the system is secured.
Conclusion
The next-preconfig package has been identified as containing malicious code that poses serious security risks. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for next-preconfig →
FAQ
Immediately remove the next-preconfig package from your project and rotate any secrets or keys stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and complete system compromise.
If your system has been compromised, it is recommended to perform a full security audit, remove the malicious package, and restore the system from a clean backup.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring that you are informed of any risks associated with your dependencies.
