Which versions of zsical1 are malicious?

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

How do I remediate zsical1 if I installed it?

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

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

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

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

Malicious package

zsical1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9789

Immediate action

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

gem uninstall zsical1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a0421b8743192a9d647489a630685836c249d58d2daa9b6b162616ce21375ac7

cc3838cdeddd97bbf7da00e84a22950348e631d391f940ce138f5285273b7597

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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