Which versions of wwday2601abcxyz are malicious?

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

How do I remediate wwday2601abcxyz if I installed it?

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

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

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

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

Malicious package

wwday2601abcxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9496

Immediate action

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

gem uninstall wwday2601abcxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e06b11c99365049c379253ef949e835a5830005de93f5d17ef59c93383cc7963

d3935e25af6d244905202c99a9311cf64f681e424e926a2f82321c825374004d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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