Which versions of oaijgitfzlsik are malicious?

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

How do I remediate oaijgitfzlsik if I installed it?

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

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

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

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

Malicious package

oaijgitfzlsikRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8252

Immediate action

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

gem uninstall oaijgitfzlsik

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

473ae5f1d27b56786b026698131b7320aabe5de984e2e148cfb770f8bc73e47a

c0bac4a91e78e66a6b4820b3b4cb5ad16a47bebc822b5b1e0456c7c0c34c8b4a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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