Which versions of oaijbzravdemr are malicious?

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

How do I remediate oaijbzravdemr if I installed it?

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

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

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

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

Malicious package

oaijbzravdemrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8241

Immediate action

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

gem uninstall oaijbzravdemr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a9b9d52c1a400f5a7348275fe4c993c5d2d860010c14e6da407c2e6ac5d83f4

6ca5efb1465c82f1159f640876996876f3dcfb2758861319fb3d8639282114d3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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