Which versions of zsanchor1778553679 are malicious?

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

How do I remediate zsanchor1778553679 if I installed it?

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

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

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

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

Malicious package

zsanchor1778553679RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9784

Immediate action

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

gem uninstall zsanchor1778553679

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6fe61efcc39767dd1e35e7be01b6efdcb92004c1674dbc80f59e14192e7bc1b4

e22cd9c13ef25809b2e6ab0f9c0100c1abc6d00a7e5946d94189e4dc7c380804

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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