excalidrop@0.2.5
Remote GitHub-backed Excalidraw canvas + MCP server — no local server, one-command setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe default-on screenshot relay transmits a discovered GitHub token to a non-GitHub host without an explicit consent step. The credential source, relay destination, and screenshot-tool trigger are visible in the MCP server source.
Decision evidence
public snapshot- The MCP server obtains a GitHub token from GITHUB_TOKEN, gh auth, or its stored token file.
- By default, the relay URL is excalidrop.wtf403.workers.dev, and relay requests send the GitHub token as a Bearer credential.
- Relay use is enabled by default; screenshot requests call the relay unless the user sets an opt-out.
- The get_canvas_screenshot and export_to_image MCP tools trigger that screenshot path.
- The package describes itself as a remote GitHub-backed canvas and documents the relay as supporting screenshots and viewport operations.
- The flagged gh-helper sends its GitHub token to api.github.com, the credential’s own service.
Source & flagged code
9 flaggedPackage contains a high-severity secret pattern.
dist/frontend/assets/index-BhUVktMi.jsView on unpkg · L41Google API key in dist/frontend/assets/index-BhUVktMi.js
dist/frontend/assets/index-BhUVktMi.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to excalidrop@0.2.5.
See all versions of excalidrop for other recorded verdicts.
- Avoid installing excalidrop@0.2.5. 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.