Which versions of roeactjs are malicious?

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

How do I remediate roeactjs if I installed it?

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

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

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

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

Malicious package

roeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7406

Immediate action

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

npm uninstall roeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

837c1a9c73424ea1e68d5900c4c3bab2e13506d8541cbbad3d86abb8795e4509

3b04a1500937c05f2924362fad8c66f555e2b6fae151a25f9d9ae5ebcb0f748d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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