Which versions of slqueryproxyabc are malicious?

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

How do I remediate slqueryproxyabc if I installed it?

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

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

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

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

Malicious package

slqueryproxyabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8776

Immediate action

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

gem uninstall slqueryproxyabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7f713ddea19c21f47906b136ee03108757e98335ecb08b5e33b81b8d95d7caf7

95e542642895220a386aa0ab4fd36a6dc46eee8e3cb8c5fb86929e5b3883aeaf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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