Which versions of micro-sharp-kit are malicious?

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

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

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

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

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

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

Malicious package

micro-sharp-kitRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

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

MAL-2026-15736

Immediate action

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

gem uninstall micro-sharp-kit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a2c85ddcabcceb944b567a23f6e759bb3c287c8c4ca8331a025651ea2d30bc86

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks micro-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