Which versions of oailamtest1 are malicious?

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

How do I remediate oailamtest1 if I installed it?

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

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

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

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

Malicious package

oailamtest1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8283

Immediate action

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

gem uninstall oailamtest1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7704c4a6628452f63429dbd7bf3a661dc08078b8b323fc748be67fcc83a3d0c5

c63584d7f7fe0d528f1de73e7aea12284e42fcec15c0194814081ff1edc71c6b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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