Which versions of lf295q15 are malicious?

The following RubyGems versions of lf295q15 are flagged malicious: 0.0.389615. Treat any of these as compromised.

How do I remediate lf295q15 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q15 (version 0.0.389615).

Malicious package

lf295q15RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q15 (RubyGems)

MAL-2026-8004

Immediate action

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

gem uninstall lf295q15

Malicious versions

1 flagged

0.0.389615

Indicators of compromise (SHA-256)

67a8253589ad9f364911dbf3b304624abdc96f65fe3f331a81a06e344c537c61

978909ee349ac62aaca6441d059f2aad3f9ee6bddc9d3d79340d60cf70e56cdb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02655RLUA-2026-08472

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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