Which versions of m8405v2llz are malicious?

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

How do I remediate m8405v2llz if I installed it?

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

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

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

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

Malicious package

m8405v2llzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8080

Immediate action

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

gem uninstall m8405v2llz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e75b4f1525f35393e498a4ef3447242975981554b4ffb8acdd0d8337315a3891

a28b503974766d19b5f5c5315706cd9ae7b9c86924de4999444b7575f8340106

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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