Which versions of slnbqotqnenc are malicious?

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

How do I remediate slnbqotqnenc if I installed it?

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

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

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

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

Malicious package

slnbqotqnencRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8645

Immediate action

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

gem uninstall slnbqotqnenc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

abc6b17f5ffb537bfa08cbdd3223405fa03c901762f598ff75bd5a3bb1680688

8fd315698df05a48dd26283da94a4db19205b5b022d825fe54e60f7b8dcb2df1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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