Which versions of eiljanlanhnz are malicious?

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

How do I remediate eiljanlanhnz if I installed it?

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

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

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

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

Malicious package

eiljanlanhnzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7654

Immediate action

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

gem uninstall eiljanlanhnz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c6995053e19e6d21caa30d78e268a733f5f4018aabbdc9edce03591bdc685892

2204fe581a343ddba2d05159328c35f7fa10ac6364f78402373ab80e84d847c8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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