Which versions of loot993 are malicious?

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

How do I remediate loot993 if I installed it?

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

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

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

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

Malicious package

loot993RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8029

Immediate action

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

gem uninstall loot993

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

38891c48dbf0637eb4627254a45161c80ed06535898830b5630fceaded35fa7c

349f74c48da3d933e82deb471e3ef1ea6b95f3ee8abdf1682c1f2238c7419915

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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