Which versions of lf295q8 are malicious?

The following RubyGems versions of lf295q8 are flagged malicious: 0.0.670623. Treat any of these as compromised.

How do I remediate lf295q8 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q8 (version 0.0.670623).

Malicious package

lf295q8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q8 (RubyGems)

MAL-2026-8011

Immediate action

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

gem uninstall lf295q8

Malicious versions

1 flagged

0.0.670623

Indicators of compromise (SHA-256)

85c460c075b5a0336b273057de6f2116f0984a8b9af31f9faa7cc0732119dfba

d32429cbd40a44fd45d37add5c7581dcf925e203bca6510dd74e15e435ee1a7c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02662RLUA-2026-08479

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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