Which versions of giga-sharp-tool are malicious?

The following RubyGems versions of giga-sharp-tool are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate giga-sharp-tool if I installed it?

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

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

Yes — giga-sharp-tool is associated with the RLMA-2026-05669 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 giga-sharp-tool across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for giga-sharp-tool (version 0.0.1).

Malicious package

giga-sharp-toolRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

giga-sharp-tool is a confirmed malicious RubyGems package (MAL-2026-15703) 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 giga-sharp-tool (RubyGems)

MAL-2026-15703

Immediate action

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

gem uninstall giga-sharp-tool

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7179ebb632a77560dc8f7f2b044521f8a6029d0ed455839e452de9cac3f6ea55

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for giga-sharp-tool (version 0.0.1).
If you installed it — respond
Remove giga-sharp-tool 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 giga-sharp-tool 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. giga-sharp-tool 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-05669

Credits

ReversingLabs · finder

Detect & block this

O3 blocks giga-sharp-tool-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