Which versions of reiactjs are malicious?

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

How do I remediate reiactjs if I installed it?

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

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

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

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

Malicious package

reiactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7383

Immediate action

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

npm uninstall reiactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

e3591ec4616bad10cd25cda9f17746c4637f4fd5a1af5cbdd76e347134282ef8

b44b271ed6f5ffd5982923f2b4760af6398aa0fc7df8fac82e08f7504f1a12cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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