Which versions of rbeactjs are malicious?

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

How do I remediate rbeactjs if I installed it?

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

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

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

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

Malicious package

rbeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7355

Immediate action

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

npm uninstall rbeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

88cac7c0452a1afa37d3c94b19a27539bcab46c8e0f266a79786c8e252fd9a6b

6ac7306053072742a3c2a06e5c3538293de6b6079569854eb2fa8b8f87d964d2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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