Which versions of watestabc128 are malicious?

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

How do I remediate watestabc128 if I installed it?

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

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

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

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

Malicious package

watestabc128RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9309

Immediate action

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

gem uninstall watestabc128

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9976040ca8ea43347b6f150aeb33775c1354ebc0767c0b3452fe86127b42fc95

b65c7e5032913690e3b6b02c179bdf75d81d53953889bf16dc91df0fe9d77c58

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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