Which versions of lp129x are malicious?

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

How do I remediate lp129x if I installed it?

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

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

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

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

Malicious package

lp129xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8034

Immediate action

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

gem uninstall lp129x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7c1203052701fb1d449ac6cc103118c28d5964deea26651f0a549fdf8edd8ba

8be9151f5b2c224f0e333871a3b0419f99824ca0b5791063da3d0d11593db0c0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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