Which versions of oailambproxy1 are malicious?

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

How do I remediate oailambproxy1 if I installed it?

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

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

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

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

Malicious package

oailambproxy1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8282

Immediate action

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

gem uninstall oailambproxy1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7553c1194f79d8820fb6a48da95a2123c74c1209672948f68d069481d364115d

ec1adc85678b20ca37de0fb06e87e3cb8a6077f8eba319fd2150942fea4f0888

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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