Which versions of nreactjs are malicious?

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

How do I remediate nreactjs if I installed it?

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

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

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

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

Malicious package

nreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7330

Immediate action

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

npm uninstall nreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

18c3b357ed66123d821165f033680f92cf614ef7a1a9cd651ba01ceed8f45bc5

c7c5d37d8a62a7e607c40762ef0de40ebf2ae80451146aec65c2129d7e06e5af

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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