Which versions of zztemp-ssf-2605 are malicious?

The following RubyGems versions of zztemp-ssf-2605 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zztemp-ssf-2605 if I installed it?

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

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

Yes — zztemp-ssf-2605 is associated with the RLMA-2026-04627, RLUA-2026-10565 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 zztemp-ssf-2605 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zztemp-ssf-2605 (version 0.0.1).

Malicious package

zztemp-ssf-2605RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zztemp-ssf-2605 is a confirmed malicious RubyGems package (MAL-2026-9976) 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 zztemp-ssf-2605 (RubyGems)

MAL-2026-9976

Immediate action

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

gem uninstall zztemp-ssf-2605

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

48c765d50a9311cc29728608ba185e30e5842c6ce099c74083bc76e8e78c3725

f72cd65b124d1157425d4ca75cc4af21360a8f164b01a18c260d23da779bdd48

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zztemp-ssf-2605 (version 0.0.1).
If you installed it — respond
Remove zztemp-ssf-2605 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 zztemp-ssf-2605 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. zztemp-ssf-2605 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-04627RLUA-2026-10565

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zztemp-ssf-2605-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