Which versions of zlx30721 are malicious?

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

How do I remediate zlx30721 if I installed it?

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

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

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

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

Malicious package

zlx30721RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9659

Immediate action

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

gem uninstall zlx30721

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7296031a6255ba719cd1850e1906afbeeae4782654763b352a77ed2adb489020

e1795a3d99ad26b45a9be2f4b752b4c45e09a876378b414d1ee3ff39a8fba846

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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