Which versions of loot995 are malicious?

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

How do I remediate loot995 if I installed it?

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

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

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

Search your lockfiles and build artifacts for loot995 (version 0.0.2).

Malicious package

loot995RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

loot995 is a confirmed malicious RubyGems package (MAL-2026-8030) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loot995 (RubyGems)

MAL-2026-8030

Immediate action

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

gem uninstall loot995

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

2da0eced228ebe721e30c4dc56010edff57a2ddb62b34c01af1a991e10320a40

6287b950594dbb79bb36e793c8104bd9d3fc1d46975af5168c79888dd736116a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02681RLUA-2026-08529

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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