Which versions of tmpgemx are malicious?

The following RubyGems versions of tmpgemx are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate tmpgemx if I installed it?

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

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

Yes — tmpgemx is associated with the RLMA-2026-03650, RLUA-2026-09574 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 tmpgemx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tmpgemx (version 0.0.1).

Malicious package

tmpgemxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

tmpgemx is a confirmed malicious RubyGems package (MAL-2026-8999) 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 tmpgemx (RubyGems)

MAL-2026-8999

Immediate action

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

gem uninstall tmpgemx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

59d5a0d28cb2010f37a6ce3c2c17c10fa21151518ca6e3069f3b039dfed837a3

84d23a0c150f6b9413f003059d91d76f137c88a25b2efd0ec32a837e8d115988

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tmpgemx (version 0.0.1).
If you installed it — respond
Remove tmpgemx 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 tmpgemx 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. tmpgemx 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-03650RLUA-2026-09574

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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