Which versions of ultra-sharp-kit are malicious?

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

How do I remediate ultra-sharp-kit if I installed it?

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

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

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

Search your lockfiles and build artifacts for ultra-sharp-kit (version 0.0.1).

Malicious package

ultra-sharp-kitRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

ultra-sharp-kit is a confirmed malicious RubyGems package (MAL-2026-15805) 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 ultra-sharp-kit (RubyGems)

MAL-2026-15805

Immediate action

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

gem uninstall ultra-sharp-kit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

caa1f6104ebb2a4d3b78c480333c55be222c8e7502c8ee44e9576b944898dbba

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ultra-sharp-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