Which versions of oaijx0156671 are malicious?

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

How do I remediate oaijx0156671 if I installed it?

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

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

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

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

Malicious package

oaijx0156671RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8261

Immediate action

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

gem uninstall oaijx0156671

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

59ac2163a5f19762b9a98c90678b9b60878487b039299182c0896adb63606de3

16e3e55bae2fa0cc6ec086b857eebdf7d4da7ff72a9a351acacdc0e85d326e8b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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