Which versions of reabctjs are malicious?

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

How do I remediate reabctjs if I installed it?

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

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

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

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

Malicious package

reabctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7359

Immediate action

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

npm uninstall reabctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

d9147ddf05407357855c4bd3cc575028c27f4a06628e696a22f5a78f13c32ea8

d472a6ab4ac4db50654dd9a759e498d6304501c72d85ad731d5c5a19884cc31e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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