Skip to content
BlurtekBlurtek
← Back to blog
Cybersecurity

GitHub's Green 'Verified' Badge Can Be Faked: What It Means

GitHub's Verified badge can be spoofed due to identity gaps and hash chain malleability. What it means for your software supply chain trust.

Blurtek
1 min read115 words
01

Yes, GitHub's green "Verified" badge can be spoofed

The badge certifies that a cryptographic signature is valid and linked to an account — not that the named person actually wrote or reviewed the code, nor that the commit chain behind it hasn't been recomposed at some point.

02

The real vector: the badge doesn't distinguish who reviewed the code

Merges done through GitHub's web interface are signed by the "web-flow" bot, not by the original authors of the commits they contain. A green badge on a merge commit doesn't guarantee every individual commit was signed by whoever claims to have written it.

At Blurtek we audit your repository and CI/CD's actual configuration, not GitHub's marketing checklist.

Request an assessment
WE START BY LISTENING

Your next step,
thought through together.

Tell us what needs to improve. We help you decide where to start and what is worth building.

Tell us about your project