Which versions of wbothg999 are malicious?

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

How do I remediate wbothg999 if I installed it?

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

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

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

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

Malicious package

wbothg999RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9316

Immediate action

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

gem uninstall wbothg999

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0199df665204a23533bb21e65819c05ce61d1aa1997f1ba2663aba5d7222eeb0

d5fdd607df10b836c784de78b1426a5614091b35a622bea9f4884f5825dda7ba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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