Which versions of wandcalq613 are malicious?

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

How do I remediate wandcalq613 if I installed it?

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

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

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

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

Malicious package

wandcalq613RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9150

Immediate action

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

gem uninstall wandcalq613

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e5779874f1a141142dbbfa02e7041b5aa22ec50cc1dc126be3076f2840c16e4c

61da3ab6cf5413bbad7de68e770bf6cf44b45518ea23c72be2ce864b135526c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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