Which versions of exfiltestwand are malicious?

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

How do I remediate exfiltestwand if I installed it?

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

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

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

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

Malicious package

exfiltestwandRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7673

Immediate action

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

gem uninstall exfiltestwand

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5a93eb669c59b7ec2760bd7bbe235f314dd7678837b7f8240abd9fdd6dcfdb2e

26338e05b7630acc4fad8fac3f76b7b776af902a10657efbf087d8cd80325c4e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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