Which versions of wybc6423a5 are malicious?

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

How do I remediate wybc6423a5 if I installed it?

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

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

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

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

Malicious package

wybc6423a5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9513

Immediate action

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

gem uninstall wybc6423a5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bcc2601689d364ce7bf2c1078ffc486d710c0dfdf843cae10c4963b064eed894

e819e4df50521b6f76e9023d7adf44c9c1c0d3103a59d061babe97f35804ab60

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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