Which versions of rneactjs are malicious?

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

How do I remediate rneactjs if I installed it?

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

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

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

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

Malicious package

rneactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7403

Immediate action

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

npm uninstall rneactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

27189bb7738ddb9a78d85094f6cbf6dfd126e40cc111f3c88bf23f1b9a80cd25

e627682cad6e2e70002f564a5f365bb5568abb803e06bec8a6b60b33025061b5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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