Which versions of micro-clean-gem are malicious?

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

How do I remediate micro-clean-gem if I installed it?

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

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

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

Search your lockfiles and build artifacts for micro-clean-gem (version 0.0.1).

Malicious package

micro-clean-gemRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

micro-clean-gem is a confirmed malicious RubyGems package (MAL-2026-15726) 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-clean-gem (RubyGems)

MAL-2026-15726

Immediate action

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

gem uninstall micro-clean-gem

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3d6f52ba35bb8c612e95c03c799867b5da641f5a4d8bc258426658bf4e0a4fef

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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