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/ngx-codemirrornpm

Advisory published Updated

@ctrl/ngx-codemirror is a confirmed malicious npm package (MAL-2025-47134) that steals credentials and exfiltrates sensitive data (malicious versions 7.0.1, 7.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/ngx-codemirror (npm)

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

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
7.0.17.0.2

Indicators of compromise (SHA-256)

06b81ae200235540464049429fd0a842ad524f50971ed856b5684ba9d5501acb
85783e56be15a96e567f02d38bd858c9738084913f6fb8445e969697e965c8b9
a32947b692ad0820f306264c5f303ceb41f0ecc53e71660138d0dc4d380cf496
e959b3fc060c019a44d266a91fee1242477eedb93379300ffa9923758de22562

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

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

Campaign

GHSA-5rr9-pf78-f78v

References

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@ctrl/ngx-codemirror (npm) malicious package — MAL-2025-47134 | O3 Security