Which versions of super-sharp-lib are malicious?

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

How do I remediate super-sharp-lib if I installed it?

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

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

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

Search your lockfiles and build artifacts for super-sharp-lib (version 0.0.1).

Malicious package

super-sharp-libRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

super-sharp-lib is a confirmed malicious RubyGems package (MAL-2026-15781) 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 super-sharp-lib (RubyGems)

MAL-2026-15781

Immediate action

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

gem uninstall super-sharp-lib

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

737ac86686ea904d3cee5827e306ea73eae62db37f07b179eaf5195037697f5e

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks super-sharp-lib-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