excalidrop@0.2.13
Remote GitHub-backed Excalidraw canvas + MCP server — no local server, one-command setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe MCP server automatically discovers GitHub credentials and sends them to the package operator's shared relay for operations. This sends a credential for another service to an external host, so the package is malicious under the credential exfiltration rule.
Decision evidence
public snapshot- The MCP server resolves GitHub credentials from GITHUB_TOKEN, gh auth, or a local token file.
- The default relay is excalidrop.wtf403.workers.dev.
- MCP relay calls send the resolved GitHub token in the Authorization header.
- The package's relay worker accepts that bearer token and uses it in requests to api.github.com.
- The package is a remote GitHub-backed canvas MCP server, so GitHub access is part of its stated purpose.
- Relay requests occur when an MCP operation is called; the worker checks access to the selected repository before forwarding the operation.
- The CLI's project and MCP configuration writes occur in its setup flow.
Source & flagged code
9 flaggedPackage contains a high-severity secret pattern.
dist/frontend/assets/index-Dtc2YcdT.jsView on unpkg · L41Google API key in dist/frontend/assets/index-Dtc2YcdT.js
dist/frontend/assets/index-Dtc2YcdT.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to excalidrop@0.2.13.
See all versions of excalidrop for other recorded verdicts.
- Avoid installing excalidrop@0.2.13. 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.