Which versions of oaipobdflfoog are malicious?

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

How do I remediate oaipobdflfoog if I installed it?

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

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

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

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

Malicious package

oaipobdflfoogRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8317

Immediate action

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

gem uninstall oaipobdflfoog

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

316977ba6678b6c55dd9570899544960ff0112a0ea5e88a20a28b30c4ed4aac7

401bac9fb39637da4a93548537f583d3c28a29194c436174a8eb83cd2e45c212

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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