Which versions of m8402v0nty are malicious?

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

How do I remediate m8402v0nty if I installed it?

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

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

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

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

Malicious package

m8402v0ntyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8066

Immediate action

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

gem uninstall m8402v0nty

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b0c3aad6368eb63b65e0727bd70f37a682402227729c92de578750dc418c7c8b

b8c6fe98f440654bbbe9924738157158707456f993d8d3f29c65d44a9515e7dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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