Which versions of areactjs are malicious?

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

How do I remediate areactjs if I installed it?

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

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

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

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

Malicious package

areactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7209

Immediate action

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

npm uninstall areactjs

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

c5a7164a895ec515d32feded393700e32f3d8f9c43a59492c6847ababe9a4e69

1d7305188b9422791e67a25acc681e7133ce38578afb3823cfd41e7b896fa68b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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