Which versions of wbotfossil999 are malicious?

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

How do I remediate wbotfossil999 if I installed it?

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

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

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

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

Malicious package

wbotfossil999RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9315

Immediate action

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

gem uninstall wbotfossil999

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87bb578b914d0232516028dc6cd042d69c94de5ff9840068a7b5c0e73fc9747b

7adab6fb9b621e57f1c388169078451c81fad3c265cf3cba8a21bd19bab3bb76

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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