Which versions of @frontembed/lib are malicious?

The following npm versions of @frontembed/lib are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @frontembed/lib if I installed it?

Remove @frontembed/lib 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 @frontembed/lib — how do I know if it already compromised me?

If @frontembed/lib 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 @frontembed/lib part of a known attack campaign?

Yes — @frontembed/lib is associated with the RLMA-2026-04722, RLUA-2026-05865 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 @frontembed/lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @frontembed/lib (version 99.99.99).

Malicious package

@frontembed/libnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@frontembed/lib is a confirmed malicious npm package (MAL-2026-7069) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @frontembed/lib (npm)

MAL-2026-7069

Immediate action

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

npm uninstall @frontembed/lib

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

d1059aa8a6168388f52ca274121d96d1a650055d11094b7a0cd8e2698c0bd039

8fe6a697462f00ab7f7334e2c07b43395154a39860e11c4f7f05324331abb28e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @frontembed/lib (version 99.99.99).
If you installed it — respond
Remove @frontembed/lib 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 @frontembed/lib 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. @frontembed/lib on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04722RLUA-2026-05865

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @frontembed/lib-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