Root cause
Package lookup could select a publicly supplied Ruby package where GitHub expected an internal dependency. A matching package name did not ensure that the package came from the intended source.
Demonstrated impact
The researcher observed code execution across multiple service contexts. The disclosed account does not establish a broader compromise beyond those observations.
What to check for
- Define explicit package sources and reserve internal namespaces where applicable.
- Treat build and developer environments as separate trust zones and minimize their credentials.
Award and evidence
How the award was verified, and what the record does not establish
The researcher states this was a critical report and that the bounty was paid; no separate payment date or public HackerOne report is supplied.
- The reward is an actual award reported in a primary researcher account; payment settlement was not independently audited.
Timeline
- Published
- 2025-10-28url_date · Date encoded in the researcher publication permalink; earliest disclosure elsewhere was not independently established.
- Public Disclosure
- 2025-10-28url_date · Date encoded in the researcher publication permalink; earliest disclosure elsewhere was not independently established.
- Reported
- 2025-09-01inferred · The timeline supplies September 1; year is inferred from the 2025 publication context.
- Awarded
- 2025-10-21inferred · The timeline supplies October 21; year is inferred from the 2025 publication context.
Related cases
- Angular automation trust and cache isolation weakness
Google · Software supply-chain security · USD 31,337
- GitHub runner-image builds shared persistent infrastructure with untrusted workflows
GitHub · Software supply-chain security · USD 20,000
- GitHub Actions trust depended on invalid repository references
GitHub · Software supply-chain security · USD 25,000
- GitHub comparison output lacked source-repository authorization
GitHub · Authorization and tenant boundaries · USD 10,000
- GitHub unsafe reflection crossed method and credential boundaries
GitHub · Injection and untrusted input · USD 75,000
Sources
- Vibecoding my way to a crit on GithubFurbreeze · reviewed 2026-10-04
Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.