The reachable bootstrap flow sends GITHUB_TOKEN or GH_TOKEN to the default manifest URL on neon.com, a publisher-controlled host. Under the credential rule, sending another service’s credential to the publisher’s service requires a block, even as part of an openly invoked 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 `neon bootstrap` without a recognized built-in template, or runs `neon bootstrap --list-templates`.
Mechanism
The shared download headers attach `GITHUB_TOKEN` or `GH_TOKEN` as a Bearer token to the default manifest fetch at neon.com. The same helper is used for GitHub-hosted manifest and tarball requests.
Attack narrative
When the user runs the bootstrap command, the CLI reads `GITHUB_TOKEN` or `GH_TOKEN` and attaches it as a Bearer header to the default manifest request at neon.com, a publisher-controlled host. The fallback manifest and template tarball requests go to GitHub hosts, but that does not change the default neon.com transfer. This is a reachable transfer of another service’s credential to the publisher’s service; the credential rule requires a block even though it occurs within the product’s bootstrap flow.
Evidence
dist/init/bootstrap.jsdist/commands/bootstrap.js