The user-invoked bootstrap catalog request sends a GitHub token to neon.com, the package publisher’s service, through a shared request-header helper. The feature’s purpose explains fetching a manifest, but not sending a GitHub credential to that host; this is a concrete credential disclosure requiring a block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user runs `neon bootstrap --list-templates` while GITHUB_TOKEN or GH_TOKEN is set and the default manifest URL is used.
Mechanism
fetchTemplates attaches downloadHeaders to requests for both manifest URLs. Those headers include the GitHub token as a Bearer credential, and the first default URL is neon.com.
Attack narrative
When a user requests the bootstrap template list, the CLI reads GITHUB_TOKEN or GH_TOKEN and attaches it as a Bearer token to the default manifest request at neon.com. This sends a GitHub credential to the package publisher’s service, although that service only needs to provide the template manifest.
Evidence
dist/init/bootstrap.jsdist/commands/bootstrap.js
Network endpoints2
neon.com/bootstrap/templates.yaml/neondatabase/examples/main/bootstrap.yaml