Which versions of lf295r2 are malicious?

The following RubyGems versions of lf295r2 are flagged malicious: 0.0.905642. Treat any of these as compromised.

How do I remediate lf295r2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295r2 (version 0.0.905642).

Malicious package

lf295r2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295r2 (RubyGems)

MAL-2026-8015

Immediate action

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

gem uninstall lf295r2

Malicious versions

1 flagged

0.0.905642

Indicators of compromise (SHA-256)

e0f4147388f4bf9110ea5aae16df7ea706b08157615bd4605963381ebdfd2d01

57abecf4aae1f2d07e524105d7994325b0dc84900f5da567ad6302ecbdfecf26

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02666RLUA-2026-08483

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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