Which versions of mreactjs are malicious?

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

How do I remediate mreactjs if I installed it?

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

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

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

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

Malicious package

mreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7323

Immediate action

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

npm uninstall mreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

170b3c92d69c77f046cf4695966d1ca6a3caf8c001faa90ef363cf152f6a00d2

8a8086ffc0a6fe037d31514e16493efac7c591114db20a9803cc47820c0b282e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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