Which versions of lp489x are malicious?

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

How do I remediate lp489x if I installed it?

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

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

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

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

Malicious package

lp489xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8044

Immediate action

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

gem uninstall lp489x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e31783e2051d3a801962d2401bb0160b0a12fc4e4d42fe9b4c4a97e1b7303f9a

fb774a3cd5de4d23c71ed6ee7bdf12f1a3941f124aa637ba3d6482f84019b169

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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