Which versions of rteactjs are malicious?

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

How do I remediate rteactjs if I installed it?

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

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

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

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

Malicious package

rteactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7411

Immediate action

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

npm uninstall rteactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

34ccb050c8e1a847d157d9ee7b6bd42bcdef78acb447da97fce397e3d855a3a6

6f73f12973e743dba99fb7661eb26dddb7c47fa2adc8da22416d50ab20d447f1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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