Which versions of ereactjs are malicious?

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

How do I remediate ereactjs if I installed it?

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

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

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

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

Malicious package

ereactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in ereactjs (npm)

MAL-2026-7279

Immediate action

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

npm uninstall ereactjs

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

7f9faa662ce12c42b39c9c76afedc9f32fad7ee7a7a23d4fb2413e63b8b50386

14e7a30e063bf274a3b80c6dd3d1afd4bea44f6f1027ad95e8da8bfbb10fc640

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ereactjs (3 malicious versions).
If you installed it — respond
Remove ereactjs 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 ereactjs 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. ereactjs on npm has been identified as a malicious package (versions 1.1.1, 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-05072RLUA-2026-06212

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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