Which versions of eilhgtestvhkue are malicious?

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

How do I remediate eilhgtestvhkue if I installed it?

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

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

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

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

Malicious package

eilhgtestvhkueRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7652

Immediate action

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

gem uninstall eilhgtestvhkue

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7567565c4a819515e54f7b852e76d80abc1a91c9e8ac15eaedb194cf5eb720e

f34fffc9d62b04c0640b5ef8dd35ddb801b49cb45e3093da4d7a66c15ee4281c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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