Which versions of giga-pure-kit are malicious?

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

How do I remediate giga-pure-kit if I installed it?

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

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

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

Search your lockfiles and build artifacts for giga-pure-kit (version 0.0.1).

Malicious package

giga-pure-kitRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

giga-pure-kit is a confirmed malicious RubyGems package (MAL-2026-15700) 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-pure-kit (RubyGems)

MAL-2026-15700

Immediate action

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

gem uninstall giga-pure-kit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8ff575e7e075d1ac604f59a594a25916a372b333bdceda54be1f7e9267cbe2f0

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks giga-pure-kit-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