Which versions of rkeactjs are malicious?

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

How do I remediate rkeactjs if I installed it?

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

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

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

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

Malicious package

rkeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7398

Immediate action

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

npm uninstall rkeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

b27556ac8611a2fbbefb859ca4c724e20b724d58602fba57287c11f13a763382

2cbfcece7a665d6a7215b36ceca0291055624118307120d8b554f482d22dceba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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