Which versions of reeactjs are malicious?

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

How do I remediate reeactjs if I installed it?

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

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

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

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

Malicious package

reeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7380

Immediate action

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

npm uninstall reeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

5087bfa920a1535028e6625ae24dbc660b40c830c48fe61a41daeb29c725d875

b74e9158b6528741872357b26dbd1ac6adcbc54daed0a5a5e5fed9e66b5082fc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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