Which versions of zwagback are malicious?

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

How do I remediate zwagback if I installed it?

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

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

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

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

Malicious package

zwagbackRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9830

Immediate action

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

gem uninstall zwagback

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f742fb0d91cf1b18be19458e6458c9210fdc39c333ef8ba0840ee165787d6330

5d88f6af0182b46dd184826c031b8323d928c0d58f4ea7e3db112f1ca960e2e1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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