Which versions of zlx4576 are malicious?

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

How do I remediate zlx4576 if I installed it?

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

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

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

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

Malicious package

zlx4576RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9660

Immediate action

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

gem uninstall zlx4576

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

21b3df66ce84d48e0451bd7241006ebd0eedb88d339126f83f78c521d74787ab

fc506bd2dd48fc036aa016a7275645ad96b0a9b82bf7a90cb2d0da417c0cfdb5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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