Which versions of zlfr18740 are malicious?

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

How do I remediate zlfr18740 if I installed it?

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

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

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

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

Malicious package

zlfr18740RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9650

Immediate action

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

gem uninstall zlfr18740

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6e2fc9883538ef10218e6b4600fd19a25e012b27515e91db245a553f2ef0e444

46b0ee94d13170c125102d5cd80a0d124639552959801b5662b37e996434f59b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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