Which versions of oaijgitjtybra are malicious?

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

How do I remediate oaijgitjtybra if I installed it?

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

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

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

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

Malicious package

oaijgitjtybraRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8253

Immediate action

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

gem uninstall oaijgitjtybra

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2b9a35d0f18ef3fcc6426d1d7b0103e6934a57eb300595ee93cf51eebef52b5e

8b928686342655712bb60ea138516933128a67cff9ee949367525869ee454c96

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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