Which versions of sq-mdc are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for sq-mdc (version 9.11.23).

Malicious package

sq-mdcRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

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

Malicious code in sq-mdc (RubyGems)

MAL-2025-192918

Immediate action

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

gem uninstall sq-mdc

Malicious versions

1 flagged

9.11.23

Indicators of compromise (SHA-256)

955b5a63ab935bfb42f5710a2e78a4bff7c0dcdd8f72072c26581a55f2de019c

d998f6442bf032c5c06658200d5be67888c2ffd3ce5a758518ca07f375bb23c8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06628RLUA-2026-09453

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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