Which versions of reachtjs are malicious?

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

How do I remediate reachtjs if I installed it?

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

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

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

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

Malicious package

reachtjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7361

Immediate action

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

npm uninstall reachtjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

c89f19f11fe72aaa084df0ff2d32fc6d80bacbdc5710e2942f887688d660858c

fd14bcd89d6d3d64a37437e4ab55e2cb9fa4d6c9f2845913a77a03d04fd59c2b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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