Which versions of rweactjs are malicious?

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

How do I remediate rweactjs if I installed it?

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

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

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

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

Malicious package

rweactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7414

Immediate action

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

npm uninstall rweactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

b72d275a095c26eed48cb029819aa6f592a344b8ec3f7eea0374f58517412799

721b1045daa0f91acd6366cd3c004647a2f76e34f820f1ab44aa3be06d8949e6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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