Which versions of lp490 are malicious?

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

How do I remediate lp490 if I installed it?

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

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

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

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

Malicious package

lp490RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8045

Immediate action

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

gem uninstall lp490

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9a2491a1d5ebc56f683b779b8901f5ec9b2d6ce2b4bf23ed096ebaa3aac2574e

628ebdc1e481c2a6b473ebae803521cc1c5826deb99e08bb717c865ab84add2e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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