Which versions of wye4ce4244 are malicious?

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

How do I remediate wye4ce4244 if I installed it?

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

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

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

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

Malicious package

wye4ce4244RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9515

Immediate action

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

gem uninstall wye4ce4244

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

403e03b2de11ae9e74e52512572948b3df151dc8b0b96d9844ca4953b0bb3207

b5ae3a7e9d4c30d5078764861484397dc59ef81bf09501b592606053b7b1c227

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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