Which versions of lp205 are malicious?

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

How do I remediate lp205 if I installed it?

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

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

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

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

Malicious package

lp205RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lp205 is a confirmed malicious RubyGems package (MAL-2026-8035) 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 lp205 (RubyGems)

MAL-2026-8035

Immediate action

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

gem uninstall lp205

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4dc23aa8feeb5a35bb278b89ada7f7d5a226258c6218b38e62ec2125dde53e6b

84ee28a889001943faf9e0517d99a76294d167c7390618ab894fe15052ba03b5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lp205 (version 0.0.1).
If you installed it — respond
Remove lp205 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 lp205 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. lp205 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-02686RLUA-2026-08534

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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