Which versions of zlfr16398 are malicious?

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

How do I remediate zlfr16398 if I installed it?

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

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

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

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

Malicious package

zlfr16398RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9648

Immediate action

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

gem uninstall zlfr16398

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

44c5635a2ae2bfd3fea7eacda9ae70f68bad542e4faa343c571fd5ab740fdd01

83146ab302eb4a6d75de5389039611881b766c62f3dfd3109da327f1779f2e83

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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