Which versions of tiny-max-gem are malicious?

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

How do I remediate tiny-max-gem if I installed it?

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

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

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

Search your lockfiles and build artifacts for tiny-max-gem (version 0.0.1).

Malicious package

tiny-max-gemRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

tiny-max-gem is a confirmed malicious RubyGems package (MAL-2026-15784) 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 tiny-max-gem (RubyGems)

MAL-2026-15784

Immediate action

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

gem uninstall tiny-max-gem

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ecc7e2a33add12848b2112c14e4c8a07eb9ae67c7706d61feb83560356c8c513

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tiny-max-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