Which versions of slnaxpliqmsh are malicious?

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

How do I remediate slnaxpliqmsh if I installed it?

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

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

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

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

Malicious package

slnaxpliqmshRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8639

Immediate action

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

gem uninstall slnaxpliqmsh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

92028a1f4ec28781f08b702772d7c6398bae161764b314388e1e94a5f3f8ba02

00fb1e4e8a5694af49b01022f1815e7abadbb5251092d9fedf2015158fdab47f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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