Critical Malicious Code Vulnerability in @legacy-ui/core Package

@legacy-ui/core Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1628: Malicious code in @legacy-ui/core (npm). Affects @legacy-ui/core versions 100.0.0. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @legacy-ui/core package is a component of the Legacy UI framework, primarily used for building user interfaces in web applications. It provides a set of reusable UI components that enhance the development process. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within version 100.0.0 of the @legacy-ui/core package. This code can potentially compromise the integrity of applications, leading to unauthorized access, data breaches, or other malicious activities. The vulnerability has been documented in the Open Source Vulnerability database, highlighting its severity and the need for immediate remediation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @legacy-ui/core

If 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, consider removing the @legacy-ui/core package from your project until a secure version is released. You can do this by running the command: npm uninstall @legacy-ui/core. Alternatively, you may explore using a different UI framework that does not have known vulnerabilities.

Conclusion

The @legacy-ui/core package has been identified with a critical vulnerability due to malicious code. It is crucial for developers to take immediate action by updating the package or implementing workarounds to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @legacy-ui/core →

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions within the application, potentially leading to data theft or system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Yes, it is recommended to update to the latest version of the @legacy-ui/core package to mitigate the risk.

Consider removing the package from your project or using an alternative UI library until a secure version is available.

Regularly monitor your dependencies using tools like Vulert, which can alert you to new vulnerabilities as they are discovered.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @legacy-ui/core

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback