Which versions of giga-safe-hub are malicious?

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

How do I remediate giga-safe-hub if I installed it?

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

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

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

Search your lockfiles and build artifacts for giga-safe-hub (version 0.0.1).

Malicious package

giga-safe-hubRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

giga-safe-hub is a confirmed malicious RubyGems package (MAL-2026-15702) 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-safe-hub (RubyGems)

MAL-2026-15702

Immediate action

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

gem uninstall giga-safe-hub

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6c93d2037c387855d3be825973b0f3c20751af7d3b9ba744b5eb5316f3426170

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks giga-safe-hub-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