Which versions of lf295q2 are malicious?

The following RubyGems versions of lf295q2 are flagged malicious: 0.0.191731. Treat any of these as compromised.

How do I remediate lf295q2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q2 (version 0.0.191731).

Malicious package

lf295q2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q2 (RubyGems)

MAL-2026-8005

Immediate action

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

gem uninstall lf295q2

Malicious versions

1 flagged

0.0.191731

Indicators of compromise (SHA-256)

aa3d8f5d72bc1fd6d5014af4da6281bf28c060a502cbe44957c4b535984b84da

f7f3b73430f8024b0044e14f9efef253bd313b097712380c52862b4dfee0c077

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02656RLUA-2026-08473

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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