Which versions of slnbpspbuqxg are malicious?

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

How do I remediate slnbpspbuqxg if I installed it?

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

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

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

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

Malicious package

slnbpspbuqxgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8643

Immediate action

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

gem uninstall slnbpspbuqxg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

13ca6be9ac10fef55f9c1a093cffdbad53eb580e720e603af09d928df1320da4

2e3c1840d5f9461eb4b385a9ac62f980d783601690f357771a8d99dace709ca7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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