Which versions of rearctjs are malicious?

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

How do I remediate rearctjs if I installed it?

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

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

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

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

Malicious package

rearctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7374

Immediate action

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

npm uninstall rearctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

2f7b3955293a60d12e467bec55c8177e9d9a165f48f8d3544dce386236407617

6d44c8f62c149bb27dd4316b6680997449d71e53e719f1dd2c356b89377d65d2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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