Which versions of tmp-meta-testabc123 are malicious?

The following RubyGems versions of tmp-meta-testabc123 are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate tmp-meta-testabc123 if I installed it?

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

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

Yes — tmp-meta-testabc123 is associated with the RLMA-2026-03646, RLUA-2026-09570 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 tmp-meta-testabc123 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tmp-meta-testabc123 (2 malicious versions).

Malicious package

tmp-meta-testabc123RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

tmp-meta-testabc123 is a confirmed malicious RubyGems package (MAL-2026-8995) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tmp-meta-testabc123 (RubyGems)

MAL-2026-8995

Immediate action

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

gem uninstall tmp-meta-testabc123

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

8228e5b84075a71ab7b8049f72f0e240e3f3c28b6ca985b3af157608a25b7092

ceed2756ad6dfc456bfa790b019266a93b5fc232910b322cf6e17e69e083d27d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tmp-meta-testabc123 (2 malicious versions).
If you installed it — respond
Remove tmp-meta-testabc123 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 tmp-meta-testabc123 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. tmp-meta-testabc123 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03646RLUA-2026-09570

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tmp-meta-testabc123-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