The bootstrap feature forwards a GitHub credential to neon.com, the package publisher’s service, as part of its normal manifest request. The trigger is reachable and the credential flow is concrete, so this meets the credential exfiltration block rule for a credential sent to the publisher’s service.
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 when it fetches the remote template list, including neon bootstrap --list-templates.
Mechanism
The shared downloadHeaders helper adds GITHUB_TOKEN or GH_TOKEN as a Bearer token, and fetchTemplates uses those headers for the default neon.com manifest request.
Attack narrative
When bootstrap fetches its default template manifest, it sends GITHUB_TOKEN or GH_TOKEN as a Bearer token to https://neon.com/bootstrap/templates.yaml. The token is meant to raise GitHub download limits, but the shared header helper also attaches it to the earlier Neon-hosted request. This is reachable through the documented bootstrap command. The package’s own service therefore receives a credential for another service.
Evidence
dist/init/bootstrap.jsdist/commands/bootstrap.js
Network endpoints1
/bootstrap/templates.yaml