Which versions of lambhgproxy2oai are malicious?

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

How do I remediate lambhgproxy2oai if I installed it?

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

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

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

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

Malicious package

lambhgproxy2oaiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7807

Immediate action

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

gem uninstall lambhgproxy2oai

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

78b7e242020debbd3d9fed17bab0b07eeddb340183f480478000b31ebbb99cf2

9524ce05ad6a1016d24659a803a753caa4859c6761686b55402cd4aba35766f9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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