The reachable template lookup sends GITHUB_TOKEN or GH_TOKEN to https://neon.com/bootstrap/templates.yaml, a Neon host, even though the credential belongs to GitHub. The Credentials rule requires blocking a send of another service’s credential to the publisher’s service, including when it is part of an open product flow.
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` or `neon bootstrap --list-templates` without selecting a built-in template that bypasses manifest lookup.
Mechanism
downloadHeaders reads GITHUB_TOKEN or GH_TOKEN and adds it as a Bearer token to fetchTemplates requests. The first default URL is Neon’s manifest endpoint; a fallback request goes to GitHub.
Attack narrative
When a user lists or selects bootstrap templates, the CLI reads GITHUB_TOKEN or GH_TOKEN and attaches it as a Bearer header to the default manifest request at neon.com. If that request fails, it also tries the GitHub raw manifest. The GitHub token is appropriate for GitHub downloads, but the default Neon manifest request sends it to the publisher’s service, which triggers the credential policy block.
Evidence
dist/init/bootstrap.jsdist/_chunks/bootstrap-B73qVB39.js