Which versions of lcomp are malicious?

The following RubyGems versions of lcomp are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate lcomp if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcomp (version 0.0.1).

Malicious package

lcompRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcomp (RubyGems)

MAL-2026-7986

Immediate action

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

gem uninstall lcomp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5304067af506941f0bec39e4aacb01c73e39b0804e7c2285e43d915d99afeecc

dfc668b13739e5041ad8250226bc499087e6bff518db51e829b4595ed7c16d52

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02637RLUA-2026-08454

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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