The source confirms that the user-run bootstrap command attaches GITHUB_TOKEN or GH_TOKEN to a request whose default destination is neon.com, the publisher’s host. Under the Credentials rule, sending another service’s credential to the publisher’s service requires a block, even when the behavior is open and part of the product; the GitHub-hosted fallback and archive requests do not remove the Neon-host path.
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 without selecting a built-in template, causing it to fetch the remote manifest.
Mechanism
The command reads GITHUB_TOKEN or GH_TOKEN, builds a Bearer header, and attaches it to the manifest request. The first default URL is neon.com; raw.githubusercontent.com is tried as a fallback. Template archives use the same helper with codeload.github.com by default.
Attack narrative
When a user runs bootstrap and the command fetches the remote template manifest, it reads GITHUB_TOKEN or GH_TOKEN and sends it as a Bearer credential to the default https://neon.com/bootstrap/templates.yaml URL. If that request fails, the same header is used for the raw.githubusercontent.com fallback. Template archive requests also carry the header to codeload.github.com. The Neon-host request sends a credential for another service to the publisher’s service, so the Credentials rule requires a block even though this is an open path in the product.