Which versions of wyb00f8cef are malicious?

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

How do I remediate wyb00f8cef if I installed it?

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

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

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

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

Malicious package

wyb00f8cefRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9512

Immediate action

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

gem uninstall wyb00f8cef

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

221e74c6251008e5cb622d127927605cdfc1ae9357735368628b17bfed6dac76

fd0251a5cb466789d56f47b00a10556aa45f6e676031cdcd981f9d1096bf7802

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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