Which versions of testtmp993 are malicious?

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

How do I remediate testtmp993 if I installed it?

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

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

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

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

Malicious package

testtmp993RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8992

Immediate action

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

gem uninstall testtmp993

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d215605d4b51178b341d77be1a234f5e0439f965c9ef92d9fc8f7ffea6a1d804

d43182185e258e0f86da10dfeb704b9d3d1483eb26f9b2413ccf17bf72d4c4c5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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