Which versions of zlam_mode12909 are malicious?

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

How do I remediate zlam_mode12909 if I installed it?

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

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

Yes — zlam_mode12909 is associated with the RLMA-2026-04290, RLUA-2026-10227 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_mode12909 across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_mode12909RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9639

Immediate action

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

gem uninstall zlam_mode12909

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

62e516709116d1e2243d73cc650978887d711948869f34b91d0d85a5b2023844

19e5231feefabadad7fea61dda57a9a832c1263023a68ae6d11d38ac20885e99

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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