Which versions of zwagweek are malicious?

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

How do I remediate zwagweek if I installed it?

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

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

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

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

Malicious package

zwagweekRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9835

Immediate action

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

gem uninstall zwagweek

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3bd0966367a805eb75eba785af21251620117ec5f5c3f233df6a125afd56a062

3a3a4beb29785f0c611819c46fa27e82921e72d3febbe197a9d2306fd471bd17

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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