Which versions of exfiltestwand4 are malicious?

The following RubyGems versions of exfiltestwand4 are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate exfiltestwand4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for exfiltestwand4 (version 0.0.4).

Malicious package

exfiltestwand4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

exfiltestwand4 is a confirmed malicious RubyGems package (MAL-2026-7676) that executes malicious code on install (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in exfiltestwand4 (RubyGems)

MAL-2026-7676

Immediate action

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

gem uninstall exfiltestwand4

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

b71657b856b7b1040f42f28cc66f389299367a7338ed0d8f1aae6b2359aee52b

5f82c01e29375ce4dccd85ce2a8f4bec434a926d996cb8a00195809f7c5fa549

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02327RLUA-2026-08072

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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