Which versions of zzlambtestf295 are malicious?

The following RubyGems versions of zzlambtestf295 are flagged malicious: 0.0.495723. Treat any of these as compromised.

How do I remediate zzlambtestf295 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zzlambtestf295 (version 0.0.495723).

Malicious package

zzlambtestf295RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zzlambtestf295 is a confirmed malicious RubyGems package (MAL-2026-9956) that executes malicious code on install (malicious version 0.0.495723). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zzlambtestf295 (RubyGems)

MAL-2026-9956

Immediate action

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

gem uninstall zzlambtestf295

Malicious versions

1 flagged

0.0.495723

Indicators of compromise (SHA-256)

d6c2235b666dfa99fce9fb0ba2a0da75eb67869f4c29b3027450f8d020e830ea

02863eafa6457bb3d15882d578e9b7cd7977f18412dcbb795e1084c50e0c1e3e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04607RLUA-2026-10545

References

Credits

ReversingLabs · finder

Detect & block this

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