Which versions of zztestno44 are malicious?

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

How do I remediate zztestno44 if I installed it?

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

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

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

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

Malicious package

zztestno44RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9985

Immediate action

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

gem uninstall zztestno44

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9405e1e22452e27e41d7d2f1f00a272dd462d48ce78e03461b6ab06c1f69fa0b

e7bfb78eb9e31d12f5c9564337786f82067a13f7f936ad0f0663844163663b94

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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