Which versions of wbotmwoy27a3 are malicious?

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

How do I remediate wbotmwoy27a3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for wbotmwoy27a3 (2 malicious versions).

Malicious package

wbotmwoy27a3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

wbotmwoy27a3 is a confirmed malicious RubyGems package (MAL-2026-9317) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wbotmwoy27a3 (RubyGems)

MAL-2026-9317

Immediate action

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

gem uninstall wbotmwoy27a3

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

ea29dc630a7320c75717907b4b24b7b498204475e6422d6106a1f5183594bec2

2a12c6db9c1f680afc69a0c249de7491224b5fd3c539c08a8d79f21ada689847

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wbotmwoy27a3 (2 malicious versions).
If you installed it — respond
Remove wbotmwoy27a3 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 wbotmwoy27a3 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. wbotmwoy27a3 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03968RLUA-2026-09898

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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