Which versions of micro-safe-tool are malicious?

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

How do I remediate micro-safe-tool if I installed it?

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

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

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

Search your lockfiles and build artifacts for micro-safe-tool (version 0.0.1).

Malicious package

micro-safe-toolRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

micro-safe-tool is a confirmed malicious RubyGems package (MAL-2026-15735) 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-safe-tool (RubyGems)

MAL-2026-15735

Immediate action

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

gem uninstall micro-safe-tool

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42ee156db1c37cd8eea06ad66d88863532b896113ec622ebe423baed3bc880a6

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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