Which versions of oaipwsgyblajm are malicious?

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

How do I remediate oaipwsgyblajm if I installed it?

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

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

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

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

Malicious package

oaipwsgyblajmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8330

Immediate action

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

gem uninstall oaipwsgyblajm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d48b85186c985b09cf0302dcd816ca3881b800d7492380bfd1365a543bb489d7

631900b7affa1b96cfbf4acf886d94c19d52986e8b8c15cad07ccd0311018cc2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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