Which versions of ireactjs are malicious?

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

How do I remediate ireactjs if I installed it?

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

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

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

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

Malicious package

ireactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ireactjs is a confirmed malicious npm package (MAL-2026-7303) 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 ireactjs (npm)

MAL-2026-7303

Immediate action

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

npm uninstall ireactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

4d816345877b65d8325a6c7a5616ecea999d8917014942527bc950c224470eed

28589df403a0263a8a3f79e9c4863b523412df5496b1355358f735d3d95313dc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ireactjs (3 malicious versions).
If you installed it — respond
Remove ireactjs 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 ireactjs 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. ireactjs 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-05119RLUA-2026-06285

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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