Which versions of rxeactjs are malicious?

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

How do I remediate rxeactjs if I installed it?

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

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

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

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

Malicious package

rxeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7415

Immediate action

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

npm uninstall rxeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

6dc21d603b2b948e993172ac62ad9ff9d6ba4f6d925369d84ba7ebd9b4fd0d62

79816ee44444cbad0f4fb8f47215242203e2d51c31580201fc4a36862c55c74f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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