Which versions of rjeactjs are malicious?

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

How do I remediate rjeactjs if I installed it?

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

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

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

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

Malicious package

rjeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7397

Immediate action

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

npm uninstall rjeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

1b224a250f3c4d9fc76d87be265db70737835f06a0846680b185303a8cef7054

78114e15a4f3aa322599e423a2d30b72e3dd890c96f98dddca01e42a6c9baa2f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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