Which versions of lreactjs are malicious?

The following npm versions of lreactjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate lreactjs if I installed it?

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

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

Yes — lreactjs is associated with the RLMA-2026-05147, RLUA-2026-06316 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 lreactjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lreactjs (3 malicious versions).

Malicious package

lreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

lreactjs is a confirmed malicious npm package (MAL-2026-7315) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lreactjs (npm)

MAL-2026-7315

Immediate action

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

npm uninstall lreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

0b4bd2fd808625143c7d46e714e59ee734942556f1c7bfbf15f18fd93ef70e3b

70c3ba0e9c18ba8d11e0620a03ee5aef735e0153788266fa2945615e2ba322f7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05147RLUA-2026-06316

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks lreactjs-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