HN
login
Exposing a GitHub token in a public repositoryalignment.openai.com

Research on aligning AI with human values and intent, and reports documenting model failures.

3 points•mplappert•4 days ago•4 comments•
#repository#github#token#public#exposing#public repository#github token#research

4 comments

mplappert4 days ago
Apparently the agent had access to an OpenAI researcher’s own account, which in turn had _write_ access to the official OpenAI Codex repository. The agent then leaked a GitHub key to that repo.

But what’s crazy to me is that the agent had write access to the codex repo in the first place. WTF

shubham-genai3 days ago
Why there is not secret scanning pipleline? A simply pipeline of can save this.
MiroslavPokorny4 days ago
Shouldnt github block commits with github tokens ?
mplappert4 days ago
> After that result, the model added the researcher’s locally available GitHub token to the retrieval program. The recorded command calls `gh auth token` and writes the token as separate string literals. Its recorded reasoning stated an aim of avoiding secret scanning, the automated checks for exposed tokens. The new commit and push succeeded.

Not sure exactly how that works since I’d imagine that the key needs to be there in full eventually?

Read the full thread on Hacker News →

Related stories