Which versions of reamctjs are malicious?

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

How do I remediate reamctjs if I installed it?

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

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

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

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

Malicious package

reamctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7373

Immediate action

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

npm uninstall reamctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

fef8b7be2837388c4aeabff4d7a6474a860c6124bdcfea8cd405a6100e8e83e2

f80a17ac92c9c41238571d6b3d4946b5f5050136c9a38d98eb676ca458ebabf0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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