Which versions of zicss110901 are malicious?

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

How do I remediate zicss110901 if I installed it?

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

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

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

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

Malicious package

zicss110901RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9579

Immediate action

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

gem uninstall zicss110901

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a7568eaedf34d66bb96c5948e879ef9d72c298bd92c26cfd2db21667d1159c37

a03a5bb15d5ac2acf9d3e3f78972af011ad1dcae8d8612dad97bcbc79124f480

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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