Which versions of rpeactjs are malicious?

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

How do I remediate rpeactjs if I installed it?

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

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

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

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

Malicious package

rpeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7407

Immediate action

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

npm uninstall rpeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

4a4ae7ea91ae7226b03a050d17697830b13763d3f5e10678af4dd36e73bf9682

52bdcffc60c3227eeebfb210a2e23b1a3b42ed29958dd35434009b5bccd1b287

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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