Which versions of rceactjs are malicious?

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

How do I remediate rceactjs if I installed it?

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

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

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

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

Malicious package

rceactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7356

Immediate action

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

npm uninstall rceactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

0a242c793185c6f119a798d29b3cf406fb9d0eb12f7ffc2abeebc77db33f43fc

2327723f45f16a8bfe72ab19be8211ef96e9d292823849e0be5b8a8443178381

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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