Which versions of lf295hgj are malicious?

The following RubyGems versions of lf295hgj are flagged malicious: 0.0.265393. Treat any of these as compromised.

How do I remediate lf295hgj if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295hgj (version 0.0.265393).

Malicious package

lf295hgjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295hgj (RubyGems)

MAL-2026-7995

Immediate action

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

gem uninstall lf295hgj

Malicious versions

1 flagged

0.0.265393

Indicators of compromise (SHA-256)

7931f786723b5187057b0cb621aa7d2bd2fe03e35dbc654e3ff3dcb5a007c129

cba65faa005a1339d83e7569fa10b07487d7eec4e40ab04cc80ae9a97c5a52c5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02646RLUA-2026-08463

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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