Which versions of QubitSDK are malicious?

The following RubyGems versions of QubitSDK are flagged malicious: 2.0.6, 2.0.7, 2.0.8, 2.0.9, 3.0.0, 3.0.2, 8.0.0. Treat any of these as compromised.

How do I remediate QubitSDK if I installed it?

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

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

Yes — QubitSDK is associated with the RLMA-2024-05079, RLUA-2024-09598 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 QubitSDK across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for QubitSDK (7 malicious versions).

Malicious package

QubitSDKRubyGems

QubitSDK is a confirmed malicious RubyGems package (MAL-2024-7006) that executes malicious code on install (malicious versions 2.0.6, 2.0.7, 2.0.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in QubitSDK (RubyGems)

MAL-2024-7006

Immediate action

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

gem uninstall QubitSDK

Malicious versions

7 flagged

2.0.62.0.72.0.82.0.93.0.03.0.28.0.0

Indicators of compromise (SHA-256)

67c23ff0c29ceee01542e1ffa7f710e3b7ae658b4be16b778230ac5353718231

5b81f48c63d977aa7fcc995e2efa12d935011c5f6e85fcf07f72033f035c15c3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for QubitSDK (7 malicious versions).
If you installed it — respond
Remove QubitSDK 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 QubitSDK 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. QubitSDK on RubyGems has been identified as a malicious package (versions 2.0.6, 2.0.7, 2.0.8, 2.0.9, 3.0.0, 3.0.2, 8.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05079RLUA-2024-09598

Credits

ReversingLabs · finder

Detect & block this

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