Which versions of oaijhghatpit are malicious?

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

How do I remediate oaijhghatpit if I installed it?

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

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

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

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

Malicious package

oaijhghatpitRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8256

Immediate action

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

gem uninstall oaijhghatpit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

895b8fceeb816f65b12c8e05effeb1bd5e8670ffe4b183caae10bfccf27d8eb9

0fde5bfe908739c2f7c697c601b1c57e9dfc391420219ab48c255ece628b09d1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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