Which versions of hyper-pro-kit are malicious?

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

How do I remediate hyper-pro-kit if I installed it?

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

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

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

Search your lockfiles and build artifacts for hyper-pro-kit (version 0.0.1).

Malicious package

hyper-pro-kitRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

hyper-pro-kit is a confirmed malicious RubyGems package (MAL-2026-15705) 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 hyper-pro-kit (RubyGems)

MAL-2026-15705

Immediate action

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

gem uninstall hyper-pro-kit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

81479c3a1bad5e4651f6d061800a5fef1e3dc595e507848a766b1ce884b9bd3d

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks hyper-pro-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