Skip to content
NewsProduct launch

GitHub blocks leaked Anthropic API keys by default, adds Salesforce as a scanning partner

· by Pondero Newsdesk

The short version

GitHub turned on default push protection for two Anthropic key formats on October 13, 2026, and added Salesforce to its secret-scanning partner program alongside a new Cloudsmith detector.

GitHub blocks leaked Anthropic API keys by default, adds Salesforce as a scanning partner

A Claude API key committed to a public GitHub repo on October 13 no longer sits there waiting to be scraped. GitHub now blocks the push itself, per its changelog entry.

What

GitHub added default push protection for two Anthropic secret formats, anthropic_service_api_key and anthropic_user_api_key. Any repository with secret scanning turned on, including free public repositories, now has commits containing those key types automatically blocked before they land, per the changelog. Salesforce separately joined GitHub's secret-scanning partner program: when a salesforce_marketing_cloud_api_oauth2_token turns up in a public repo, GitHub now forwards it directly to Salesforce so the credential can be revoked or rotated before anyone can abuse it. The same release added a plain detector (not covered by default push protection) for Cloudsmith's cloudsmith_api_key.

Push protection catches Claude keys before they ship

Secret scanning without push protection only tells a developer after the key is already in the repo's history, visible to anyone with clone access and, on a public repo, to anyone on the internet. Push protection moves the check earlier, rejecting the commit at the moment it would leave the developer's machine. That timing matters most for the exact workflow driving a lot of current GitHub traffic: someone wiring an agent or a script to Claude, dropping a key into a config file or a notebook cell, and pushing before thinking about .gitignore. Free public repositories get the same default blocking as paid plans, so a solo developer vibe-coding a side project is covered the same way an enterprise team is.

Context and reactions

The Salesforce addition runs through a separate mechanism: GitHub still detects the exposed salesforce_marketing_cloud_api_oauth2_token and alerts the repo owner, but it also forwards the finding directly to Salesforce so Salesforce itself can revoke or rotate the credential, per the changelog. That direct-to-issuer forwarding only covers public repos. It matters more as teams connect AI agents to existing SaaS accounts: an agent script wired to Salesforce Marketing Cloud now has a second line of defense if its token leaks, on top of whatever the developer notices on their own.

What to watch next

Watch for GitHub to extend default push protection to other frontier-model API key formats the same way it just did for Anthropic, and for Cloudsmith's new detector to graduate from plain detection to a default-blocked type in a future release. Developers relying on free public repos should also check whether any existing Anthropic keys were exposed before October 13, since the new protection only blocks new pushes, not secrets already sitting in a repo's history.

Sources