Which versions of oaiphawmupjos are malicious?

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

How do I remediate oaiphawmupjos if I installed it?

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

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

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

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

Malicious package

oaiphawmupjosRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8310

Immediate action

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

gem uninstall oaiphawmupjos

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

add91779e657dc9cb93595f42e25c60357fb68f8db2f8c4e1b16f0a31a9d0fc6

0d40e23429fc744dab6d7480eed713d4c86ce426e6cf9a308958ae573d1426ca

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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