Which versions of zlx19317 are malicious?

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

How do I remediate zlx19317 if I installed it?

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

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

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

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

Malicious package

zlx19317RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9658

Immediate action

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

gem uninstall zlx19317

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a256fbcc10f9e8accf7b7a8468801d7cbfc3dfb702f21ed4606ec43a6627d8f6

d752fee30bae8595926e546e9490883ab0a9517a429faafebf1a261abe03f159

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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