Critical Malicious Code Vulnerability in legacy-shared-frontend Package
Summary
MAL-2026-1768: Malicious code in legacy-shared-frontend (npm). Affects legacy-shared-frontend 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-shared-frontend package is a component used in npm ecosystems, primarily designed for shared frontend functionalities across various applications. It provides essential features that facilitate the development of user interfaces. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the legacy-shared-frontend package stems from the introduction of malicious code that can compromise the integrity of applications utilizing this package. This issue originated from a malicious actor who injected harmful scripts into version 100.0.0 of the package. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and the ability for attackers to execute arbitrary code within the affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall legacy-shared-frontendIf 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-shared-frontend package from your project until a secure version is released. This can be done using the command: npm uninstall legacy-shared-frontend. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The legacy-shared-frontend package has been identified with a critical vulnerability due to malicious code injection. It is imperative for developers using this package to take immediate action by updating to a secure version or removing the package altogether to protect their applications from potential threats.
See every vulnerability recorded for legacy-shared-frontend →
FAQ
It is an npm package designed for shared frontend functionalities in web applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.
The risks include unauthorized access to sensitive data, potential data breaches, and execution of arbitrary code.
Yes, updating to a patched version of the legacy-shared-frontend package is recommended to mitigate the vulnerability.
Consider removing the package from your project as a temporary measure until a secure version is available.
