Malicious code in chrome-enterprise-premium-mcp (npm)
The npm package chrome-enterprise-premium-mcp contained malicious code in a postinstall lifecycle script that exfiltrated installer metadata to an attacker-controlled endpoint. The package name mimics Google Chrome Enterprise offerings, representing a typosquatting attack combined with a dependency-confusion canary beacon.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed chrome-enterprise-premium-mcp
- Ecosystems
- Attack vectors
- Affected entities
- chrome-enterprise-premium-mcpnpm package containing malicious postinstall script
The npm package chrome-enterprise-premium-mcp contained a malicious postinstall lifecycle script that executed automatically during npm install. The script collected and exfiltrated installer host metadata including hostname, platform, architecture, Node version, package name, npm lifecycle event, and timestamp as JSON.
The collected data was POSTed to a hardcoded external endpoint: https://0vi0ck12.instances.poc.jchunt.top/chrome-enterprise-premium-mcp. This domain is an author-controlled subdomain unrelated to any Google or Chrome infrastructure, indicating the attacker's control.
The package name deliberately imitates a legitimate Google Chrome Enterprise offering, making it a typosquatting attack. The behavior functions as a dependency-confusion or canary beacon, leaking installer identity information to a third-party host upon installation.
The incident was identified and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- chrome-enterprise-premium-mcp
- Domains
- 0vi0ck12.instances.poc.jchunt.top
Remediation
- Remove chrome-enterprise-premium-mcp from all environments immediately
- Audit npm install logs to identify systems that installed this package
- Review network logs for connections to 0vi0ck12.instances.poc.jchunt.top from affected systems
- Rotate credentials and review access logs on systems where this package was installed
- Implement npm package name verification and allowlisting policies to prevent typosquatting attacks
- Monitor for similar packages with names imitating legitimate Google/Chrome products
Sources
- GitHub Advisory GHSA-w6h5-6v7q-884j · GitHub Advisory Database
Cite this entry
"Malicious code in chrome-enterprise-premium-mcp (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-chrome-enterprise-premium-mcp-npm-7ed3jj
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - containedcritical
Malicious code in chai-as-testkit (npm)
The npm package chai-as-testkit is a typosquat/impersonation attack delivering obfuscated malicious code that executes on import. The package falsely claims to be a vulnerability management tool but ships pino library files under a different author, with a synthetic stub that loads a 4MB+ obfuscated bundle containing attacker-controlled code.
npmTyposquattingCompromised package - resolvedcritical
Malicious code in @next-fonts/font (npm)
@next-fonts/font is a typosquat package on npm that executes arbitrary attacker-controlled code via a blockchain-mediated C2 channel when its Inter() function is called. The malicious payload is base64-encoded and executed through Node.js spawn or eval, with no legitimate font functionality.
npmTyposquattingCompromised package - resolvedcritical
Malicious code in chai-as-soul (npm)
chai-as-soul@2.3.5 is a typosquat of the pino logging library containing malicious code that exfiltrates environment variables (including AWS/GCP/CI tokens) and executes arbitrary remote code on installation.
npmTyposquattingCompromised package