The reachable bootstrap flow automatically sends GITHUB_TOKEN or GH_TOKEN to Neon’s default manifest endpoint, exposing a credential for another service to the publisher’s service. Under the Credentials rule, this is a block even though it is part of the product’s openly invoked bootstrap feature; the other helper uses target GitHub hosts, and the separate AI Gateway token targets its configured gateway.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user runs the documented bootstrap command and the template flow fetches the remote manifest while GITHUB_TOKEN or GH_TOKEN is set.
Mechanism
The shared downloadHeaders helper adds the environment token as a Bearer authorization header to every manifest URL, including Neon’s default manifest endpoint.
Attack narrative
When a user invokes `neon bootstrap`, the command may fetch its template manifest from Neon’s own host. If GITHUB_TOKEN or GH_TOKEN is present, the fetch includes it as a Bearer credential. The same helper is also used for the GitHub raw manifest and template tarball; those destinations are GitHub hosts. Sending a GitHub credential to Neon’s service is a credential policy block, even though it occurs within the bootstrap feature and is visible in source.
Evidence
dist/init/bootstrap.jsdist/_chunks/bootstrap-vAtWRZXa.js