Which versions of zlmeet016311 are malicious?

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

How do I remediate zlmeet016311 if I installed it?

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

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

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

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

Malicious package

zlmeet016311RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9656

Immediate action

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

gem uninstall zlmeet016311

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

553169609ddcd73f29ae7dedebb83923f6ec374af11ae652812006c5c43a7324

5a253d0221eaf0df588b913908720f57fa4f16cc1f6a92bd650a463430afb077

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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