Which versions of zlam_agenda are malicious?

The following RubyGems versions of zlam_agenda are flagged malicious: 0.0.202. Treat any of these as compromised.

How do I remediate zlam_agenda if I installed it?

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

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

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

Search your lockfiles and build artifacts for zlam_agenda (version 0.0.202).

Malicious package

zlam_agendaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_agenda (RubyGems)

MAL-2026-9615

Immediate action

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

gem uninstall zlam_agenda

Malicious versions

1 flagged

0.0.202

Indicators of compromise (SHA-256)

cf1b4cbda926614a9f588b8960bdb1400404d3cf643fe5ee19428b6eab2d21b8

80f61708aa296390704eb31843a31ce2ef8152503d059d1512606e1582d0d846

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04266RLUA-2026-10203

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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