Which versions of wandday26x are malicious?

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

How do I remediate wandday26x if I installed it?

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

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

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

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

Malicious package

wandday26xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9187

Immediate action

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

gem uninstall wandday26x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

da4bcafd111451f824fdae7e9161a8da7064c731bd830eb31bbe638b9801d1d4

87668e31c55d86390256c4c7c3ff6f34bee258978caf64c0c9ea01a9f00fc937

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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