Which versions of hyper-sharp-box are malicious?

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

How do I remediate hyper-sharp-box if I installed it?

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

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

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

Search your lockfiles and build artifacts for hyper-sharp-box (version 0.0.1).

Malicious package

hyper-sharp-boxRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

hyper-sharp-box is a confirmed malicious RubyGems package (MAL-2026-15709) 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-sharp-box (RubyGems)

MAL-2026-15709

Immediate action

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

gem uninstall hyper-sharp-box

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fdd05d6677d6f8c9f93589281a99507a875cb4d843540c89ef51b7379ff1ff91

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks hyper-sharp-box-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