Which versions of zsagenda1 are malicious?

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

How do I remediate zsagenda1 if I installed it?

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

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

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

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

Malicious package

zsagenda1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9783

Immediate action

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

gem uninstall zsagenda1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

39ae7896cf009145dcd96e1b1c0a6cc53902616d0ec7c1b1e40af1fe635f75d6

5b7daaadd6ad1abf5f2c6da18bb9d965f91a87832654820c2cc38c7a62906587

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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