Which versions of slncbiuaqy are malicious?

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

How do I remediate slncbiuaqy if I installed it?

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

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

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

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

Malicious package

slncbiuaqyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8654

Immediate action

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

gem uninstall slncbiuaqy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9e15edb85d2b54779e80e70c0bb1e373cf1aca776f534119eac5d89666b6f03f

6244ed5fec1cc0f73c0d817961bbb677b3b363111438b9f15d71d002b399a21a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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