Which versions of @saif777/codemirror5 are malicious?

The following npm versions of @saif777/codemirror5 are flagged malicious: 7.66.5. Treat any of these as compromised.

How do I remediate @saif777/codemirror5 if I installed it?

@saif777/codemirror5 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.

I already installed @saif777/codemirror5 — how do I know if it already compromised me?

If @saif777/codemirror5 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 @saif777/codemirror5 part of a known attack campaign?

Yes — @saif777/codemirror5 is associated with the GHSA-pm5r-8qx2-2m4r 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 @saif777/codemirror5 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @saif777/codemirror5 (version 7.66.5).

Malicious package

@saif777/codemirror5npm

Advisory published Apr 29, 2026Updated May 5, 2026

@saif777/codemirror5 is a confirmed malicious npm package (MAL-2026-3185) that steals credentials and exfiltrates sensitive data (malicious version 7.66.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @saif777/codemirror5 (npm)

MAL-2026-3185

Immediate action

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

npm uninstall @saif777/codemirror5

What this malware does

Dependency confusion and typosquatting campaign by threat actor "saif777". Packages use inflated version numbers (9999.9999.9999, 9999.9999.10000, 50.50.50, 7.66.5) to win version resolution in environments with private registries. All active packages execute a postinstall hook ("node index.js") that collects a system fingerprint — public IP (via api.ipify.org), username, hostname, CPU model, RAM, working directory, OS platform — and exfiltrates it as a Discord embed to a shared webhook (base64-obfuscated in source). Payloads include sandbox/bot detection: machines with ≤1 CPU or <2 GB RAM are flagged as sandbox/CI; real machines trigger a green embed. Typosquats the CodeMirror 5 editor library using a fake scoped package name.

The package @saif777/codemirror5 was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified '@saif777/codemirror5' @ 7.66.5 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

7.66.5

Indicators of compromise (SHA-256)

05a16b6c187f8c3c5ab4c2c62627e75d9f8d14d28d265854e57ba1cb33bb7f3b

d8c90f2fd5697c867e9bb88102c93cf144662dcee32b95e0ad2a27061c867c65

8db9cd375e8cbbf22e45deec617d9a841313ef4c2ed262275ee24d58d48d8bd0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @saif777/codemirror5 (version 7.66.5).
If you installed it — respond
@saif777/codemirror5 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.
Did it already run?
If @saif777/codemirror5 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. @saif777/codemirror5 on npm has been identified as a malicious package (version 7.66.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pm5r-8qx2-2m4r

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks @saif777/codemirror5-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