vulns.co
/
GKData.io MCP and API Buy me a coffee

GitHub · Software supply-chain security

GitHub package-source trust allowed dependency confusion

GitHub build and development services could confuse internal Ruby packages with packages from a public source. The researcher observed code execution in several service contexts and reports a $20,000 award for one finding. The account does not establish a wider compromise beyond those observations.

Read the original writeupUSD 20,000 reported award · Reviewed 2026-10-04

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

USD 20,000Bug Bounty · Researcher Reported
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

All 4 cases in Software supply-chain security

Sources

  1. Vibecoding my way to a crit on GithubFurbreeze · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software