Which versions of wandmine24680 are malicious?

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

How do I remediate wandmine24680 if I installed it?

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

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

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

Search your lockfiles and build artifacts for wandmine24680 (2 malicious versions).

Malicious package

wandmine24680RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

wandmine24680 is a confirmed malicious RubyGems package (MAL-2026-9231) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wandmine24680 (RubyGems)

MAL-2026-9231

Immediate action

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

gem uninstall wandmine24680

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

5af19215cc5c50b1121b324042b26e0a2ba25b0b80f31b07b34ef440553a0817

1bd121d9a8fe30a2cd9268ea3e0ab31c6a02ca11aa2e01343f76e5c3fbce47e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wandmine24680 (2 malicious versions).
If you installed it — respond
Remove wandmine24680 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 wandmine24680 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. wandmine24680 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03882RLUA-2026-09812

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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