Which versions of ltestprobe are malicious?

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

How do I remediate ltestprobe if I installed it?

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

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

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

Search your lockfiles and build artifacts for ltestprobe (2 malicious versions).

Malicious package

ltestprobeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8053

Immediate action

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

gem uninstall ltestprobe

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

781026eb02edc2cb49c202e4c4bf8b6dbff8a7d2aec386a38ce0af4788ffdc78

3575cc3ff1989503a3c973f2e0d51ad3c67e0a9cec26de1fee2c6774faf3962a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ltestprobe (2 malicious versions).
If you installed it — respond
Remove ltestprobe 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 ltestprobe 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. ltestprobe 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-02704RLUA-2026-08552

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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