Which versions of zztestownedtmp1 are malicious?

The following RubyGems versions of zztestownedtmp1 are flagged malicious: 0.0.9810. Treat any of these as compromised.

How do I remediate zztestownedtmp1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zztestownedtmp1 (version 0.0.9810).

Malicious package

zztestownedtmp1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zztestownedtmp1 (RubyGems)

MAL-2026-9986

Immediate action

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

gem uninstall zztestownedtmp1

Malicious versions

1 flagged

0.0.9810

Indicators of compromise (SHA-256)

aff6fa4e9263a81aad9897b4a74d4bdcae8d3983308d1f538b10f25e812df4e3

e8754590635942d670c6bd0aabb87edabd3fa8c67d8dae3e42ae5607c51e98b3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04637RLUA-2026-10575

References

Credits

ReversingLabs · finder

Detect & block this

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