Which versions of oaipuetanenak are malicious?

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

How do I remediate oaipuetanenak if I installed it?

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

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

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

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

Malicious package

oaipuetanenakRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8327

Immediate action

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

gem uninstall oaipuetanenak

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fdf735f236839469abdf5f78449b6d70c0350933130bbfc674a0da058a090d17

6f030721bfe5048737b30817d750e08633e23c414df533b3b4b72915d6b76000

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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