Which versions of watestabc123 are malicious?

The following RubyGems versions of watestabc123 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate watestabc123 if I installed it?

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

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

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

Search your lockfiles and build artifacts for watestabc123 (version 0.0.1).

Malicious package

watestabc123RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in watestabc123 (RubyGems)

MAL-2026-9304

Immediate action

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

gem uninstall watestabc123

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ae83824e542214fd96134833ee262994d65ca8e82a1c683424a8d6384eb39f4a

bdd98e1be9b3fbf0bbe8d27178c9091b5f92d421b86a2aacfa8c719aacac92e8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03955RLUA-2026-09885

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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