Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @ctrl published 14 malicious packages. See the full campaign →
Malicious package

@ctrl/qbittorrentnpm

Advisory published Updated

@ctrl/qbittorrent is a confirmed malicious npm package (MAL-2025-47138) that steals credentials and exfiltrates sensitive data (malicious versions 9.7.1, 9.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/qbittorrent (npm)

MAL-2025-47138
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ctrl/qbittorrent

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged
9.7.19.7.2

Indicators of compromise (SHA-256)

af92aa639259dc9a287445d9fdbb2ec61beeb5adf71ff13a6e8f9bceb79971a2
53f3d8cf0440eb1391766f9e08aa3847b9f156e98b7e2f6ead5a71dcfe155dde
79cdb5d8af1062d73ef2a744cc00f473081f40b0eb5fba84ee62bea3fd646b4f
3453e70c26a52c5c705187cd4dd4d85b1d83bd5ab38f4930c528972eabc9881f

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @ctrl/qbittorrent (2 malicious versions).

  2. If you installed it — respond

    @ctrl/qbittorrent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @ctrl/qbittorrent 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. @ctrl/qbittorrent on npm has been identified as a malicious package (versions 9.7.1, 9.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c4cx-7q75-vjq5

References

Detect & block this

O3 blocks @ctrl/qbittorrent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@ctrl/qbittorrent (npm) malicious package — MAL-2025-47138 | O3 Security