Which versions of slnblctcmige are malicious?

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

How do I remediate slnblctcmige if I installed it?

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

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

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

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

Malicious package

slnblctcmigeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8641

Immediate action

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

gem uninstall slnblctcmige

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f5562c798a3eff77c00d2d1769d83b856fd665c5e2dbde509109012e30970ac3

7e0b70e1214b4f06ddd057c30170e6dbf74e7321872b04650186cf55087b7804

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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