Which versions of watestabc126 are malicious?

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

How do I remediate watestabc126 if I installed it?

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

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

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

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

Malicious package

watestabc126RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9307

Immediate action

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

gem uninstall watestabc126

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cdfebac3d762c291efdcd5956a76b9f23ff068aedd08d8f38c9d447faed59c5d

cb48c7207813b3b866019fa573bc74e6bb9db820a0608ecaeadbe7017f95814a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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