Which versions of oaijhgzfujin are malicious?

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

How do I remediate oaijhgzfujin if I installed it?

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

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

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

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

Malicious package

oaijhgzfujinRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8260

Immediate action

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

gem uninstall oaijhgzfujin

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f388c258027c14e519124d265a6dfba55d46954771f86c43e8906ddf467be9f2

9b235d88df875ab3fd23bae7ff5d5bdf0c9a8e9c26df011b1b9bb881566f937e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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