Which versions of rseactjs are malicious?

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

How do I remediate rseactjs if I installed it?

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

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

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

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

Malicious package

rseactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7410

Immediate action

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

npm uninstall rseactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

3ee09a5119676af93d1dbbf3c361aa2adeb7d2ccd87799efe16208aed58a9424

b885aef097bfc7348a4a2cec1b9fe236b9ca5dc384532817f8db7e4f91cd57db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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