Which versions of eiljanlambpfwo are malicious?

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

How do I remediate eiljanlambpfwo if I installed it?

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

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

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

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

Malicious package

eiljanlambpfwoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7653

Immediate action

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

gem uninstall eiljanlambpfwo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88b0146cf51f2a918d75d00a8ba6e8b77b52c0cfbe4a425d1911a66ed57bb349

7d1870aab70bf26d93f47eb41f7e82ead784ab7a90fdeb265a6f2a3a0917eba5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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