Which versions of wwday2801txtxyz are malicious?

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

How do I remediate wwday2801txtxyz if I installed it?

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

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

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

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

Malicious package

wwday2801txtxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9501

Immediate action

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

gem uninstall wwday2801txtxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50d7b76cf02fe257c6548e3248b1fadab9d1734f5858392d5565c3d2e48af0f6

66083377f6f5d7ddf8cc667d99815bbe0efcf0b62869ea5c8b43ecb6796e6cee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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