Which versions of zlfr1135 are malicious?

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

How do I remediate zlfr1135 if I installed it?

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

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

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

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

Malicious package

zlfr1135RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9646

Immediate action

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

gem uninstall zlfr1135

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a9680baed1763fdfae498ab7b141b450c4348268344da9f6533235184d236a3e

383791fd46673e4e5a934bea6cb0a199e6915900d49e36168188dcfbf5ca1b33

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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