Which versions of zlfr20694 are malicious?

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

How do I remediate zlfr20694 if I installed it?

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

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

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

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

Malicious package

zlfr20694RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9652

Immediate action

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

gem uninstall zlfr20694

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3b23df1d37e7c93e0c02b58b56996865a187336d3d4ec8b6595c8d2dd09cd6ed

016d33967d187907d080583a8b7a1100cb20b1c10fb1f30027ff8ffbd5fbfdb3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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