Which versions of ztestlamb01 are malicious?

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

How do I remediate ztestlamb01 if I installed it?

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

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

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

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

Malicious package

ztestlamb01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9810

Immediate action

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

gem uninstall ztestlamb01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bf58864225a3052775e193da4f4b9108d2f3ebc93b84743bc653385f7f185be8

a83cf3a510dcd5609d24eececc36bfac60dc646a90570a8883edc066ad42c528

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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