Which versions of m8402v3uig are malicious?

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

How do I remediate m8402v3uig if I installed it?

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

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

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

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

Malicious package

m8402v3uigRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8069

Immediate action

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

gem uninstall m8402v3uig

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9288cc35be4094806a70e2c3361dceebbcb2ee44c5e51fb7063ccd09ec08d98f

ec19834f9884b885cef2622704c979ccc0552aee96320821ead98a84dd3e8c9a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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