Which versions of rgeactjs are malicious?

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

How do I remediate rgeactjs if I installed it?

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

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

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

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

Malicious package

rgeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7394

Immediate action

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

npm uninstall rgeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

791307857067c30bc2f99d367b7c1ffe9cbd667c20480d3f3d7a5de8e056b98a

c358272bc0610797957c42c5358717141a332828cbd2c288953bc5c189698404

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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