Which versions of zwagback2 are malicious?

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

How do I remediate zwagback2 if I installed it?

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

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

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

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

Malicious package

zwagback2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9831

Immediate action

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

gem uninstall zwagback2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c51c0c70902641c72a72bc441a1ea06441ad0736e31c2c33c27bdeaf72ba7490

fa79d2d56f8979df9fc02a8fb5d09d50c5c824ba9b94553b90fc292f74640f35

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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