Which versions of wwday3001txtxyz are malicious?

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

How do I remediate wwday3001txtxyz if I installed it?

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

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

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

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

Malicious package

wwday3001txtxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9505

Immediate action

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

gem uninstall wwday3001txtxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1d55dd3c5ad24d3a06eb913b0097284e03cae954fb85e26eca9b975980a7db88

d4e2c73f2c6a223430ec2b20af67d6805ab4dbc6e46da5a0a6f540858c73ab41

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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