Which versions of @legacy-ui/core are malicious?

The following npm versions of @legacy-ui/core are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate @legacy-ui/core if I installed it?

Remove @legacy-ui/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @legacy-ui/core — how do I know if it already compromised me?

If @legacy-ui/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @legacy-ui/core part of a known attack campaign?

Yes — @legacy-ui/core is associated with the RLMA-2026-01023 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @legacy-ui/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @legacy-ui/core (version 100.0.0).

Malicious package

@legacy-ui/corenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@legacy-ui/core is a confirmed malicious npm package (MAL-2026-1628) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @legacy-ui/core (npm)

MAL-2026-1628

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @legacy-ui/core

What this malware does

The package @legacy-ui/core was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

3b00901c52a8789da2e478b29b4363d19b03cccaa94e71f165a7318d40d48cb4

9cc68fa0af265da13a26ccfc943668c887b5aa3f4a73ddc7af9ab2d8498d7a0d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @legacy-ui/core (version 100.0.0).
If you installed it — respond
Remove @legacy-ui/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @legacy-ui/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @legacy-ui/core on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01023

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @legacy-ui/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database