Which versions of watestabc124 are malicious?

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

How do I remediate watestabc124 if I installed it?

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

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

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

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

Malicious package

watestabc124RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9305

Immediate action

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

gem uninstall watestabc124

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

798de885f10cd3d53f582a7e1c9bbc17718865ff37192c580222821be2e9e89a

d77a034ad9f93bf645332b5912db2ce39f91d514241f950e94cd91b09c1454f1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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