Which versions of lf295r0 are malicious?

The following RubyGems versions of lf295r0 are flagged malicious: 0.0.248998. Treat any of these as compromised.

How do I remediate lf295r0 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295r0 (version 0.0.248998).

Malicious package

lf295r0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295r0 (RubyGems)

MAL-2026-8013

Immediate action

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

gem uninstall lf295r0

Malicious versions

1 flagged

0.0.248998

Indicators of compromise (SHA-256)

cfdb27eb0b2a7d27c542a9e74c96c9937f6a6226e47760078b774fb6a548bb50

aae7466d5ecbd3641559a5e65db59acc65597880d860697528c28c9ef60963c5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02664RLUA-2026-08481

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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