Which versions of sq-samsa are malicious?

The following RubyGems versions of sq-samsa are flagged malicious: 12.3.1. Treat any of these as compromised.

How do I remediate sq-samsa if I installed it?

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

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

Yes — sq-samsa is associated with the RLMA-2025-06629, RLUA-2026-09455 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 sq-samsa across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sq-samsa (version 12.3.1).

Malicious package

sq-samsaRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

sq-samsa is a confirmed malicious RubyGems package (MAL-2025-192919) that executes malicious code on install (malicious version 12.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sq-samsa (RubyGems)

MAL-2025-192919

Immediate action

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

gem uninstall sq-samsa

Malicious versions

1 flagged

12.3.1

Indicators of compromise (SHA-256)

747b2859bfd1e44a4a4e80a7245bc80a14175bf4931d0997b53da9dca3f7aa07

fb3c7a6aced2263e163ef1e6fbd5d9caf3a49bddb6cf983943c22274682232de

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sq-samsa (version 12.3.1).
If you installed it — respond
Remove sq-samsa 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 sq-samsa 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. sq-samsa on RubyGems has been identified as a malicious package (version 12.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06629RLUA-2026-09455

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sq-samsa-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