Which versions of rmeactjs are malicious?

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

How do I remediate rmeactjs if I installed it?

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

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

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

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

Malicious package

rmeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7400

Immediate action

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

npm uninstall rmeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

9c15a494a95309341037c79bb4bbda6ebd9ca47e3d6f5fe156b2fe3f81dfc27f

9cc5c9427f13e472c38a5b53221ed178911772cda81b0f3f9c4a9fc64ae0a4a9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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