Which versions of zlam_demo11842 are malicious?

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

How do I remediate zlam_demo11842 if I installed it?

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

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

Yes — zlam_demo11842 is associated with the RLMA-2026-04274, RLUA-2026-10211 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_demo11842 across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_demo11842RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_demo11842 is a confirmed malicious RubyGems package (MAL-2026-9623) 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_demo11842 (RubyGems)

MAL-2026-9623

Immediate action

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

gem uninstall zlam_demo11842

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4a6bfe666a3f9b03f44c1f16aefb56d88d45ca94557c9458e88a1998329a31b5

0fa7686d4a19aaf09c54ff71b5e0d80a245989b2a3ca5a810e71b32a7ea009a5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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