Which versions of wwday2601txtxyz are malicious?

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

How do I remediate wwday2601txtxyz if I installed it?

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

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

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

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

Malicious package

wwday2601txtxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9497

Immediate action

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

gem uninstall wwday2601txtxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

118022b771fae880c73b2c458cbdf92b92bf412379a862f31f8706f96b0af7a2

e25c3a86124a5de0a902a7a65ce04973bb914d7cbc4f0fcb044037fcaec48e8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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