Which versions of zlfr13581 are malicious?

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

How do I remediate zlfr13581 if I installed it?

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

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

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

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

Malicious package

zlfr13581RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9647

Immediate action

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

gem uninstall zlfr13581

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

40873aabd7465d7ef11ed475b927d654e13bfe2c5c453b962e7e326b90af60c5

dde5d69634b5149d8c353c1392e28915643fa1c87dd8ab77bea1c11b6358aab3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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