Which versions of sygit1778552745 are malicious?

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

How do I remediate sygit1778552745 if I installed it?

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

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

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

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

Malicious package

sygit1778552745RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8965

Immediate action

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

gem uninstall sygit1778552745

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

332511269818b7db9bf6f6932f0bd2a7da3e06b7474d399ece460ebb3719a416

e79b2411b6b0825a5b7e91482131ecd62a6419f0c505df9604fb086eece30ecd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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