Which versions of watestabc129 are malicious?

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

How do I remediate watestabc129 if I installed it?

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

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

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

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

Malicious package

watestabc129RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

watestabc129 is a confirmed malicious RubyGems package (MAL-2026-9310) 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 watestabc129 (RubyGems)

MAL-2026-9310

Immediate action

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

gem uninstall watestabc129

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7b5df4ff50786af00b2d4ea3b27dd58639f013fdac54af2f30a2adb918e02252

0b98133298ce13bac073be5a81170db0bf24d117d1955fc3c73f997ecd173d2a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for watestabc129 (version 0.0.1).
If you installed it — respond
Remove watestabc129 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 watestabc129 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. watestabc129 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-03961RLUA-2026-09891

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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