Which versions of cuatest889 are malicious?

The following RubyGems versions of cuatest889 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate cuatest889 if I installed it?

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

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

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

Search your lockfiles and build artifacts for cuatest889 (version 0.0.2).

Malicious package

cuatest889RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

cuatest889 is a confirmed malicious RubyGems package (MAL-2026-7604) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cuatest889 (RubyGems)

MAL-2026-7604

Immediate action

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

gem uninstall cuatest889

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

5982c1b2e1901161d89c0462c35259b6b01969908417b5a1eb224d3ae25a2306

a282acd31d9e16535c5464ee9ddf0280bb92a40806afe41b6502362a4ef5cd32

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cuatest889 (version 0.0.2).
If you installed it — respond
Remove cuatest889 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 cuatest889 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. cuatest889 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02255RLUA-2026-07948

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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