Which versions of legacy-shared-frontend are malicious?

The following npm versions of legacy-shared-frontend are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate legacy-shared-frontend if I installed it?

Remove legacy-shared-frontend 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-shared-frontend — how do I know if it already compromised me?

If legacy-shared-frontend 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-shared-frontend part of a known attack campaign?

Yes — legacy-shared-frontend is associated with the RLMA-2026-01398 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-shared-frontend across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for legacy-shared-frontend (version 100.0.0).

Malicious package

legacy-shared-frontendnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

legacy-shared-frontend is a confirmed malicious npm package (MAL-2026-1768) 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-shared-frontend (npm)

MAL-2026-1768

Immediate action

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

npm uninstall legacy-shared-frontend

What this malware does

The package legacy-shared-frontend was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

e8507a73cce0bbb77cb7a9692e550619a6949cbeea0fe8fb6f94315cf48d51c7

e0bdad0c7ae6723e92b1d0bc357ec0ed147ccb057cba4fc6cff4a2a26d7cc967

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for legacy-shared-frontend (version 100.0.0).
If you installed it — respond
Remove legacy-shared-frontend 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-shared-frontend 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-shared-frontend 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-01398

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks legacy-shared-frontend-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