GitHub users (phishing campaign reported by GitHub) (2022): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
GitHub users (phishing campaign reported by GitHub) disclosed the incident on 16 Sep 2022. What was exposed, as the sources state it: GitHub stated that the campaign affected many victim organizations, and that in many cases the threat actor downloaded private repository contents accessible to the compromised user; GitHub itself was not affected.
Open the ledger · Report a correction
- Disclosed
- 16 Sep 2022
- Incident window
- From September 2022
- Cloud or provider
- GitHub
- What was exposed
- GitHub stated that the campaign affected many victim organizations, and that in many cases the threat actor downloaded private repository contents accessible to the compromised user; GitHub itself was not affected.
- How access was gained
- GitHub stated that a phishing site imitating the GitHub login page stole credentials and relayed TOTP codes to the threat actor in real time, and that accounts protected by hardware security keys were not vulnerable.
- Access path
- Stolen user credentials and session tokens
- Kind of control that addresses it
- require hardware security keys or other phishing-resistant authentication for source-control accounts
In the words of the source
“Clicking the link takes the user to a phishing site that looks like the GitHub login page but steals any credentials entered.” (company statement, Security alert: new phishing campaign targets GitHub users)
Primary sources
- company statement: Security alert: new phishing campaign targets GitHub users, dated 16 Sep 2022
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- Security alert: new phishing campaign targets GitHub users, read 16 Nov 2026
Last reviewed 16 Nov 2026.