Which versions of watestabc127 are malicious?

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

How do I remediate watestabc127 if I installed it?

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

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

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

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

Malicious package

watestabc127RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9308

Immediate action

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

gem uninstall watestabc127

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b6c8d36dddad4825619daebcc153152dd4369ec86e86985b6608cbcebfcdf197

737460671c99b3855a2d1f03e5ddd9e792501eacf1f7f9985ddf5c90006f9b7f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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