Which versions of ureactjs are malicious?

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

How do I remediate ureactjs if I installed it?

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

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

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

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

Malicious package

ureactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7430

Immediate action

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

npm uninstall ureactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

30bbe32f47ea83b3bf110be8985f7a36ee48e73622dec1327a9eb2bea0718cb3

20fc7f922bd1ff88d8a9d054d18cf31bb212252d982c0a1b0c0b88801608be06

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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