Which versions of zztestno33 are malicious?

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

How do I remediate zztestno33 if I installed it?

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

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

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

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

Malicious package

zztestno33RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9984

Immediate action

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

gem uninstall zztestno33

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1b84bf0cf6e6833fe00f41f6f1ceb6630c44e3ae18809d1d305675edaa4500c7

49d7d94140346f462c28c726658d8b1eef0d79d5089718ee7ff5487f637f4ed2

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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