Which versions of zwagq are malicious?

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

How do I remediate zwagq if I installed it?

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

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

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

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

Malicious package

zwagqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9834

Immediate action

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

gem uninstall zwagq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a421151efe353520dc3f76a1f48923ffe1694c5591f12dbd585ce5d7d49765d2

6fbe8facb882cab19817dae6101208cb39745c668ff8d433d8e04b044c458e75

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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