Which versions of eiljtpfoucdt are malicious?

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

How do I remediate eiljtpfoucdt if I installed it?

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

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

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

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

Malicious package

eiljtpfoucdtRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7657

Immediate action

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

gem uninstall eiljtpfoucdt

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bb6ac6c7f97abfc591892e0a864202bf1fd2b8c918876a6084a841c689acdf4f

029329454c8f460d016b5cb70e8a140e4d78749930a16e49ea536ba6a508db61

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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