Which versions of rdeactjs are malicious?

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

How do I remediate rdeactjs if I installed it?

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

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

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

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

Malicious package

rdeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7357

Immediate action

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

npm uninstall rdeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

f9e691e4fc1facf4cd3611e1189d90e1f3bec9cb0105e7074f701df47eb15e52

2257a7cd3a0bd29b314e14485cef47fd0c0acade410d0d2bd29172187e969a09

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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