Which versions of ryeactjs are malicious?

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

How do I remediate ryeactjs if I installed it?

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

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

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

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

Malicious package

ryeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7416

Immediate action

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

npm uninstall ryeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

84ae20a05ce851d965020b6b4430a0f688bcce89b26205af67512541ad4dbe3a

350e9462e759fa9e353bdcfcbbd775fd669c41df3713b1a71d4534e926d8a64d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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