Which versions of lf295r1 are malicious?

The following RubyGems versions of lf295r1 are flagged malicious: 0.0.845828. Treat any of these as compromised.

How do I remediate lf295r1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295r1 (version 0.0.845828).

Malicious package

lf295r1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295r1 (RubyGems)

MAL-2026-8014

Immediate action

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

gem uninstall lf295r1

Malicious versions

1 flagged

0.0.845828

Indicators of compromise (SHA-256)

9f71e9df13cd860c00cfbce59768a4d48f29d4ec111d5ea48a94f3839b865f11

aeff60f8f8fc852858dc882c7e0879eccbf076a672637d24420253a114dc9695

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02665RLUA-2026-08482

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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