Which versions of wwday2701txtxyz are malicious?

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

How do I remediate wwday2701txtxyz if I installed it?

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

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

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

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

Malicious package

wwday2701txtxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9499

Immediate action

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

gem uninstall wwday2701txtxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

442172ad2ad37d5c2d6a16a85745c47654c2491732bf73496db25dd70f21e003

5d1fad00c3b1da7fd6286a634affbd22a1d6f3decdacd1a8794f2ba97187af21

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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