Which versions of m8249v1gsl are malicious?

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

How do I remediate m8249v1gsl if I installed it?

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

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

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

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

Malicious package

m8249v1gslRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8055

Immediate action

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

gem uninstall m8249v1gsl

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3fbeac71dd0f7edca7b462db6c95f66b710896f91b223a1fa1456c56f4b6d703

b217da6fce59759acad98d0f82caf35c237c4e0e6f2330e422533ff7bd118b28

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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