Malicious Code Vulnerability in @legacy-components/core Package
Summary
MAL-2026-1627: Malicious code in @legacy-components/core (npm). Affects @legacy-components/core versions 100.0.0. 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 @legacy-components/core package is a component library designed for building user interfaces in web applications. It provides a set of reusable components that enhance development efficiency and maintainability. However, this package has been identified as having a serious vulnerability that could allow malicious code execution, compromising the integrity of applications that rely on it.
Vulnerability Detail
The vulnerability in the @legacy-components/core package stems from the inclusion of malicious code that can execute unauthorized actions within an application. This issue was reported on March 18, 2026, and is linked to version 100.0.0 of the package. If exploited, this vulnerability could lead to data breaches, unauthorized access, and potential system compromise. The malicious code was identified through a security analysis conducted by ReversingLabs.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @legacy-components/coreIf 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 workaround, you can remove the @legacy-components/core package from your project until a secure version is released. This can be done using the following command:
npm uninstall @legacy-components/core
Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @legacy-components/core package has a critical vulnerability due to the presence of malicious code. It is essential to take immediate action by updating the package or implementing workarounds to mitigate risks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for @legacy-components/core →
FAQ
The vulnerability involves malicious code that can execute unauthorized actions within applications using the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
As a temporary measure, consider uninstalling the package or using alternative libraries until a secure version is available.
The vulnerability was discovered by ReversingLabs, a security research organization.
Failure to address this vulnerability could lead to data breaches, unauthorized access, and significant security risks for your application.
