Which versions of lage-npm are malicious?

The following npm versions of lage-npm are flagged malicious: 99.12.9. Treat any of these as compromised.

How do I remediate lage-npm if I installed it?

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

If lage-npm 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 lage-npm part of a known attack campaign?

Yes — lage-npm is associated with the RLMA-2026-05136, RLUA-2026-06298 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 lage-npm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lage-npm (version 99.12.9).

Malicious package

lage-npmnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

lage-npm is a confirmed malicious npm package (MAL-2026-7308) that executes malicious code on install (malicious version 99.12.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lage-npm (npm)

MAL-2026-7308

Immediate action

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

npm uninstall lage-npm

Malicious versions

1 flagged

99.12.9

Indicators of compromise (SHA-256)

5c9b5add598558a474c171d3412162d61974beb738017f1e2cc595c48b610600

ae58460e8bfea311476f4570ca1567a4a2b3b5cfe49d53ff40d1e3ec53fc0337

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05136RLUA-2026-06298

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks lage-npm-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