Which versions of wreactjs are malicious?

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

How do I remediate wreactjs if I installed it?

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

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

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

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

Malicious package

wreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7441

Immediate action

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

npm uninstall wreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

fd15e08821a3e6812a42c0e7fa978d61e34eec9b838f00240fb4b06cd181a368

28d6a60b8a4a14928146f385d0b0c9c767f63066dbdf95102950d3a5ec311470

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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