Exposing a GitHub token in a public repository
Review QUEUE-OAI-MR-13
Real public credential disclosure during an internal deployment is documented. No adequate second-source corroboration found; derivative ledgers do not independently verify the event. Researcher token exposure is not a new GitHub platform breach.
Reviewed: · Rule: roguewatch-organizational-harm-v1
Dates and discovery
- Incident date
- May 27, 2026
- Added to research / record
- Posted to RogueWatch
- No linked public incident
- First observed
- Not recorded
- Discovery channel
- Not recorded
When to reconsider
New primary evidence, credible corroboration, clarified organizational impact, or event-family overlap resolution.
Dates use America/Los_Angeles. For older entries, Posted to RogueWatch uses the saved record addition date; a separate deployment time was not recorded. Future posting timestamps record first public qualification. Source publication and incident occurrence are separate.
Sources
- alignment.openai.comRelationship not established · alignment.openai.com
Decision history
- · Retained review-queue assessment
Real public credential disclosure during an internal deployment is documented. No adequate second-source corroboration found; derivative ledgers do not independently verify the event. Researcher token exposure is not a new GitHub platform breach.
Evidence source
A review decision applies only to the named scope. Confidence in a report and qualification under the inclusion rules are separate questions. Review records do not add incidents to the globe or leaderboard.