Which versions of oreactjs are malicious?

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

How do I remediate oreactjs if I installed it?

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

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

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

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

Malicious package

oreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7333

Immediate action

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

npm uninstall oreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

66b0ba43b2e71a53a4c217ae8f59aaa52c7c078827a6d5a16d9b621267062f93

3274f34a9620befdcff42893989ae316f7ed046908127c2d421b3f31ae926114

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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