Which versions of lai67123812 are malicious?

The following RubyGems versions of lai67123812 are flagged malicious: 0.0.70812. Treat any of these as compromised.

How do I remediate lai67123812 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lai67123812 (version 0.0.70812).

Malicious package

lai67123812RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lai67123812 (RubyGems)

MAL-2026-7784

Immediate action

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

gem uninstall lai67123812

Malicious versions

1 flagged

0.0.70812

Indicators of compromise (SHA-256)

5a7879818655cccc9eef4369ac5b3f27c15862b5f9e8913c0f3689869ffb4b36

dd40460173f992df065ce3c6ac5634941713f1422cfdec51972e7568afd7c5b4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02435RLUA-2026-08250

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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