Which versions of eilsvntestanumw are malicious?

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

How do I remediate eilsvntestanumw if I installed it?

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

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

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

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

Malicious package

eilsvntestanumwRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7659

Immediate action

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

gem uninstall eilsvntestanumw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e3bbf9c2cd20da7be3a19f1ae3e585b64af8a78802668a58573599360089a4c1

5abd33f32d4d1523215be1c97f2c92ad2813954f5348af1f955b938178c7bd07

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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