Which versions of wandsyardresabc are malicious?

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

How do I remediate wandsyardresabc if I installed it?

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

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

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

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

Malicious package

wandsyardresabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9299

Immediate action

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

gem uninstall wandsyardresabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bbfd0eb8e1a5984e2198911e6de30e38219a53c1c05b7ab2a6087c1cba6850cd

495c1b5aceda760e370b36c4c733a04e0d0ad88164ca9eeec8dcbdd001956d1d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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