Critical Malicious Code Vulnerability in next-circular-dependency Package
Summary
MAL-2025-190979: Malicious code in next-circular-dependency (npm). Affects next-circular-dependency versions 1.0.2 – 1.0.3. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The next-circular-dependency package is an npm library designed to manage circular dependencies in JavaScript projects. It is commonly used in various applications to ensure that modules can reference each other without causing issues during loading. However, this package has been found to contain malicious code, posing significant risks to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the next-circular-dependency package, which has been identified to contain embedded malicious code. This code can compromise any computer that has the package installed or running, leading to potential data breaches and unauthorized access to sensitive information. Users are advised to consider their systems fully compromised if this package is present, as it may allow external entities to gain control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall next-circular-dependencyIf 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, you can temporarily replace the functionality provided by next-circular-dependency with custom code that handles circular dependencies without relying on this malicious package. However, it is highly recommended to remove the package entirely.
Conclusion
The next-circular-dependency package poses a significant security risk due to the presence of malicious code. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for next-circular-dependency →
FAQ
You should immediately uninstall the package using 'npm uninstall next-circular-dependency' and rotate any sensitive information stored on the affected system.
You can use the Vulert platform 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.
The risks include potential data breaches, unauthorized access to sensitive information, and complete control of the affected system by external entities.
No, there are currently no patched versions available for this package. The only solution is to uninstall it.
Yes, but you may need to implement alternative solutions to handle circular dependencies in your code.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
