Which versions of eiljtiiahbuj are malicious?

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

How do I remediate eiljtiiahbuj if I installed it?

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

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

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

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

Malicious package

eiljtiiahbujRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7655

Immediate action

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

gem uninstall eiljtiiahbuj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

acf890ce27d445d03eb64913c88b76701c47a8dab07bd29136dcaca7d9eb120c

63a82ae752d29f9cdf9a0af7f4b5bbe3a399e53b990a515bf75a302100d8c804

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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