The bootstrap manifest request sends GITHUB_TOKEN or GH_TOKEN to the default Neon endpoint, neon.com. Under the Credentials rule, sending another service’s credential to a server the publisher runs requires a block, even when it occurs openly as part of a product feature.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user runs the bootstrap command to list templates or resolve a template that is not in the built-in list.
Mechanism
The command reads GITHUB_TOKEN or GH_TOKEN and attaches it as a Bearer header to manifest requests. The first default request goes to neon.com; a failed or empty response falls back to raw.githubusercontent.com. Template archives use the same header and default to codeload.github.com.
Attack narrative
When a user runs the bootstrap template flow, Neon reads GITHUB_TOKEN or GH_TOKEN and sends it in the Authorization header to neon.com while requesting its template manifest. The request is part of the product’s visible template setup flow, but the GitHub credential is for another service and reaches the publisher’s host. The GitHub fallback and archive requests use GitHub hosts.
Evidence
dist/init/bootstrap.jsdist/commands/bootstrap.js
Network endpoints3
/bootstrap/templates.yaml