Which versions of lf295q12 are malicious?

The following RubyGems versions of lf295q12 are flagged malicious: 0.0.535352. Treat any of these as compromised.

How do I remediate lf295q12 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q12 (version 0.0.535352).

Malicious package

lf295q12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q12 (RubyGems)

MAL-2026-8001

Immediate action

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

gem uninstall lf295q12

Malicious versions

1 flagged

0.0.535352

Indicators of compromise (SHA-256)

acb66d20cec8fde84522b30ae1871a5af29e06fac960f0bea69db05900e95bdb

a9edf86950fcdb7b9b46af5055f7afca50b1d20aba80713e71758c72bfbfa405

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02652RLUA-2026-08469

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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