Which versions of oaijbzrevovmk are malicious?

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

How do I remediate oaijbzrevovmk if I installed it?

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

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

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

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

Malicious package

oaijbzrevovmkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8242

Immediate action

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

gem uninstall oaijbzrevovmk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

897055ca1a68070b6015be08421ef8809b57f1315b2b335d39c1b5b69959da07

3414c8b9bcc38eb30df45b699c07d34d8697d902becc9ad15e986a5e7db0e7db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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