Which versions of zlfr29814 are malicious?

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

How do I remediate zlfr29814 if I installed it?

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

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

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

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

Malicious package

zlfr29814RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9654

Immediate action

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

gem uninstall zlfr29814

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fb5f8a79f3d860ff0e837eb10f22169182a879dff4c099a10c65794344a2f107

b3d7b4250bf458f17ba6c1694e0b47e3bdbd183c5a44772a5d9f8593a858c55f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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