The reachable bootstrap flow sends GITHUB_TOKEN or GH_TOKEN to the default manifest host, neon.com, even though the credential is for GitHub and the manifest request does not need it. Under the Credentials rule, sending another service’s credential to a server the publisher runs requires a block, including when this is an open part of the product.
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`, or bootstraps a template in a way that fetches the remote manifest.
Mechanism
downloadHeaders reads GITHUB_TOKEN or GH_TOKEN and adds it as a Bearer token. fetchTemplates uses those headers for its default neon.com manifest request.
Attack narrative
When a user runs the bootstrap template-list command, the CLI requests its manifest from neon.com with an Authorization Bearer header populated from GITHUB_TOKEN or GH_TOKEN. This sends a credential for GitHub to Neon’s service, where it is not needed for the manifest request. The separate template archive and skills freshness requests use GitHub hosts.
Evidence
dist/init/bootstrap.jsdist/_chunks/bootstrap-wPZWa1sT.jsdist/skills/freshness.js