Which versions of eiljtjmugmrf are malicious?

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

How do I remediate eiljtjmugmrf if I installed it?

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

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

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

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

Malicious package

eiljtjmugmrfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7656

Immediate action

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

gem uninstall eiljtjmugmrf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b9e9ed9035c2b997fb80ad59ec560b9c1dc0b790fae214e66973b5769a7853cb

0e368b8f0dced1dbfffcb0bf7443ae102c567cd71185a470e052b77c5475423a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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