cursor-browser-cli
CLI + MCP to drive Cursor IDE's built-in Browser Tab from Grok Build, Claude Code, Codex, or shell
This report shows the evidence for cursor-browser-cli@1.2.2. 4 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package’s postinstall mutates broad, foreign AI-agent control surfaces and registers an MCP integration without consent. Localhost-only networking does not mitigate this install-time control-surface change.
Decision evidence
public snapshot- postinstall runs setup automatically.
- Setup copies a skill into Codex, Claude, Grok, Cursor, and generic agent roots.
- Setup invokes Grok MCP removal/addition without user action.
- Installed extension exposes browser automation through a localhost bridge.
- MCP network client targets only 127.0.0.1.
- No remote endpoint or credential-exfiltration code found in inspected sources.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
scripts/setup.jsView on unpkg · L48Findings
Affected versions and remediation
This report applies to cursor-browser-cli@1.2.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing cursor-browser-cli@1.2.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.