Which versions of rebactjs are malicious?

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

How do I remediate rebactjs if I installed it?

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

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

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

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

Malicious package

rebactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7379

Immediate action

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

npm uninstall rebactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

fac1b8ab7f93064f0f5b3db7409bb0088e46cf432cd3544c6e689cfac3c870dd

8856b7c55e77b5760938cc7131c9236d40804009316a82ac70d4e92b08fcf9cb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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