Which versions of oailamtest3 are malicious?

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

How do I remediate oailamtest3 if I installed it?

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

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

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

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

Malicious package

oailamtest3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8285

Immediate action

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

gem uninstall oailamtest3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9261415c0090ac4556e63c95c294436ba1b6c306e4b66c733519981160866d55

a189b1623b371851a8dc6c04573f7dbc745b5ba911f9bcbf62833f31123d4def

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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