Which versions of testwandyg3hook are malicious?

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

How do I remediate testwandyg3hook if I installed it?

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

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

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

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

Malicious package

testwandyg3hookRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8993

Immediate action

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

gem uninstall testwandyg3hook

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5b826f1444e3e7e1460617892c77f9e618312fa96602b2046583a0bd9f10908f

ca9bf35990bde2560f1ddc75d32a58c3874da5f953b931c2b5414ae35d69ea11

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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