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/magnet-linknpm

Advisory published Updated

@ctrl/magnet-link is a confirmed malicious npm package (MAL-2025-47133) that steals credentials and exfiltrates sensitive data (malicious versions 4.0.3, 4.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/magnet-link (npm)

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

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
4.0.34.0.4

Indicators of compromise (SHA-256)

f96e0d70a5cb3964405f7aba9078b5161152b463c1d39a33de953fd10cee2c41
e8e9638c683be2cbf402e760305c1b3dd57b3fded27dcdfa6e4b47e6e59f75c2
7c175fbbd7f09b824696b799fcab314ac8b7e69ba2a7ed811ad4238317036992
2a907e0437c92444a128b6db437fa8b0e43dfe250da53a0c1c30f344778877ec

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

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

Campaign

GHSA-487x-8rm3-h5j5

References

Detect & block this

O3 blocks @ctrl/magnet-link-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/magnet-link (npm) malicious package — MAL-2025-47133 | O3 Security