Which versions of zztest4098 are malicious?

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

How do I remediate zztest4098 if I installed it?

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

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

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

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

Malicious package

zztest4098RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9983

Immediate action

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

gem uninstall zztest4098

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fb1c52f4761cd7b1302eb965ca553585841ceb5b6f430e1ed459766287e53d21

f1ee4563b254ab95d62e00c29168402554d7dfddc4362b83e495f2768edf76e7

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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