Which versions of lf295s0 are malicious?

The following RubyGems versions of lf295s0 are flagged malicious: 0.0.107824. Treat any of these as compromised.

How do I remediate lf295s0 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295s0 (version 0.0.107824).

Malicious package

lf295s0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295s0 (RubyGems)

MAL-2026-8016

Immediate action

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

gem uninstall lf295s0

Malicious versions

1 flagged

0.0.107824

Indicators of compromise (SHA-256)

e2190e5910270bac7aac9eed133318522ec58c1f966ce123b9eccb4434b3bc28

8e5ccc1128eec0f71211d1437b605599d3eec29a0c94cb2996a959d4c1a812a7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02667RLUA-2026-08484

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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