Which versions of wwday2901txtxyz are malicious?

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

How do I remediate wwday2901txtxyz if I installed it?

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

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

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

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

Malicious package

wwday2901txtxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9503

Immediate action

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

gem uninstall wwday2901txtxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

13ef81272e6874c13e4827f0c25870bc2476356696ad8196fe03d2bed8325dbd

ef0a1778ce76f092e78d874521be1efcbdb5912500797a5279f471f0d380edc8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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