Which versions of wwday2701abcxyz are malicious?

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

How do I remediate wwday2701abcxyz if I installed it?

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

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

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

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

Malicious package

wwday2701abcxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9498

Immediate action

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

gem uninstall wwday2701abcxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f9a4757c0e2a37f9b66a72bd7ebe70ada61187922b70177ec80bc8d27d16279a

acbed725fb6de5dddddaa93ea7d0dee1dae48f11b1112b977f71131f2ef98c37

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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