Which versions of zsbing1 are malicious?

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

How do I remediate zsbing1 if I installed it?

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

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

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

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

Malicious package

zsbing1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9785

Immediate action

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

gem uninstall zsbing1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

db4169a93f10b7d5fa0a666bf7ee084de160f1bbd1e0a3f4ab3b3c7da364d591

587d6de1af1b7e71a7ec72d0d72b914f69fbacedd9b21919c3e5a469d0856cfd

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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