Which versions of oaicx3769699 are malicious?

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

How do I remediate oaicx3769699 if I installed it?

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

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

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

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

Malicious package

oaicx3769699RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8160

Immediate action

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

gem uninstall oaicx3769699

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a557f4432424c96bf4bff13df4cfa51baa3b7f02718c3d7cfba7705d0f9494c

05467ab6ab201042f5d21cf0a1017b0b2d635dd78dda164be1cb910e550d72bd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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