Which versions of slncfffqbi are malicious?

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

How do I remediate slncfffqbi if I installed it?

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

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

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

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

Malicious package

slncfffqbiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8658

Immediate action

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

gem uninstall slncfffqbi

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

446297381965743c1fb222a25221b32f04f4199003236f96eabe2e7cd53878dc

ad713433b73b5e8ad51f59373b1ccc5bc87fd741f06507ba5a9a651b9de39660

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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