Which versions of lf295q5 are malicious?

The following RubyGems versions of lf295q5 are flagged malicious: 0.0.295929. Treat any of these as compromised.

How do I remediate lf295q5 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q5 (version 0.0.295929).

Malicious package

lf295q5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q5 (RubyGems)

MAL-2026-8008

Immediate action

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

gem uninstall lf295q5

Malicious versions

1 flagged

0.0.295929

Indicators of compromise (SHA-256)

550f957d3b7c702a773e074faa94ab5a63398b4323d6030a7824317d92ec7192

bf855e0a6f5deae2202e4ed7183f0e4e15a317a25e13a8701b88670d09bb4b4b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02659RLUA-2026-08476

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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