Which versions of zzzltestfoobarxyz are malicious?

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

How do I remediate zzzltestfoobarxyz if I installed it?

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

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

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

Search your lockfiles and build artifacts for zzzltestfoobarxyz (2 malicious versions).

Malicious package

zzzltestfoobarxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zzzltestfoobarxyz is a confirmed malicious RubyGems package (MAL-2026-10005) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zzzltestfoobarxyz (RubyGems)

MAL-2026-10005

Immediate action

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

gem uninstall zzzltestfoobarxyz

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

e91c8951992f46945e55784a67e3d9c90a18e5ad586c93c530c0f73278a812a8

d884ae9773dd81f4a5725c72aedf02d7cafcaa2b181885f66499590034b517ba

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zzzltestfoobarxyz (2 malicious versions).
If you installed it — respond
Remove zzzltestfoobarxyz 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 zzzltestfoobarxyz 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. zzzltestfoobarxyz on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04656RLUA-2026-10594

References

Credits

ReversingLabs · finder

Detect & block this

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