Which versions of m8249v5qnb are malicious?

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

How do I remediate m8249v5qnb if I installed it?

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

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

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

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

Malicious package

m8249v5qnbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8059

Immediate action

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

gem uninstall m8249v5qnb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5c774fc55aef8edcc699d064adf9ef9ed47ae8723c8e68b066546eadea8c1fc5

9c590311dc1100839c741e1f1ac103d0bad7b0733e641054eeeb75a90390669e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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