Skip to main content
Mallory
← Back to News
leaked-secret-api-keybuild-pipeline-compromisecloud-misconfigurationthird-party-vendor-breach

Home Depot Internal Systems Exposed via Leaked GitHub Token

Breach & Incident Intelligence · 2 sources · Updated 5mo ago · First seen Dec 13, 2025

Home Depot Internal Systems Exposed via Leaked GitHub Token

A security researcher discovered that a Home Depot employee had inadvertently published a private GitHub access token online, which remained exposed for approximately a year. The token granted access to hundreds of private source code repositories, as well as critical internal systems such as order fulfillment, inventory management, and code development pipelines. The researcher attempted to alert Home Depot multiple times but received no response until the issue was escalated through media contact, after which the exposure was remediated.

The exposed credential provided not only read but also write permissions to sensitive repositories and cloud infrastructure, significantly increasing the risk of unauthorized modifications or data breaches. Home Depot has since removed the leaked token from public view, but the incident highlights the dangers of credential leakage and the importance of timely response to security disclosures. The company has hosted much of its developer infrastructure on GitHub since 2015, making such exposures particularly impactful.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Jan 1, 2024 – Dec 12, 2025
  1. Dec 12, 202511mo ago

    Home Depot removes exposed credential after media inquiry

    Home Depot removed the credential from public view only after TechCrunch contacted the company for comment. This action ended the public exposure described by the researcher.

  2. Dec 12, 202511mo ago

    Zimmermann makes multiple disclosure attempts to Home Depot

    After identifying the exposed token, Zimmermann reportedly tried several times to notify Home Depot about the issue. According to the reports, the company did not respond to those outreach attempts.

  3. Dec 12, 202511mo ago

    Researcher Ben Zimmermann discovers the exposed Home Depot token

    Security researcher Ben Zimmermann found the leaked credential and determined that it could be used to access private GitHub repositories and parts of Home Depot's cloud infrastructure. His findings established the scope and duration of the exposure.

  4. Jan 1, 20243y ago

    Exposed credential leaves Home Depot internal systems accessible for about a year

    For roughly a year after the token was published, the exposed credential reportedly allowed access to internal Home Depot resources, including systems tied to order fulfillment and inventory management. The exposure persisted without remediation during that period.

  5. Jan 1, 20243y ago

    Home Depot employee token is accidentally published on GitHub

    A private GitHub access token belonging to a Home Depot employee was accidentally exposed in a public GitHub repository in early 2024. The credential reportedly granted write access to private Home Depot repositories and access to cloud-connected internal systems.

Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.