Critical Malicious Code Vulnerability in @consts/links Package
Summary
MAL-2026-17202: Malicious code in @consts/links (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
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 @consts/links package is a JavaScript library used in Node.js applications, primarily for managing and providing constant links throughout an application. It is designed to streamline the process of link management, ensuring consistency and ease of use. However, this package has been identified to contain malicious code, posing significant security risks to any application utilizing it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @consts/links 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 implications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @consts/linksIf 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
There are no effective workarounds for this vulnerability other than removing the package entirely and ensuring that all sensitive information is secured.
Conclusion
The @consts/links package contains malicious code that poses a significant security risk to any system using it. Immediate action is required to remove the package and secure any sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for @consts/links →
FAQ
You should remove the package immediately and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
While removing the package is essential, you should also rotate all sensitive information and consider rebuilding your application to ensure no remnants of the malicious code remain.
If a patched version is released, updating may resolve the issue. However, due to the nature of the compromise, it is crucial to take additional security measures.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
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.
