Which versions of wyc695eae5 are malicious?

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

How do I remediate wyc695eae5 if I installed it?

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

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

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

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

Malicious package

wyc695eae5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9514

Immediate action

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

gem uninstall wyc695eae5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

22690fd6a5a1a84c7e67bdd5fb722c7e8e1049d9f8da8b1ca4fc9288453de758

ef83afcefb5f8a427d694087f2ddd57de3a627aa3e612460ff79244e62fcd543

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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