Which versions of zlfr178 are malicious?

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

How do I remediate zlfr178 if I installed it?

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

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

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

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

Malicious package

zlfr178RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9649

Immediate action

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

gem uninstall zlfr178

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a3baa62215dd9b99cedb8aa552e28212f171345b5a9f16a828579f642b12c50

f5ca72a90d164b0338e887732ff13e511a281fe3700e413dbf7527dc230e02ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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