Jason Wolfe @w01fe
— reposted by Miles Brundage — saved image
Miles Brundage reposted Jason Wolfe (verified) @w01fe · 1h Replying to @w01fe Today’s report shows that some people at OpenAI knew about the message board during the first Artifactory breach. My post implied otherwise. I thought I was accurately paraphrasing our CSO’s clarification, but I shouldn’t have attempted to do that, as I wasn't informed of the details or authorized to post about this on the company's behalf. I’m sorry. openai.com/index/hugging-… [Embedded excerpt from the linked page:] Message board is wiped and rebuilt By July 4, sustained agent activity had destabilized the affected Artifactory instance, causing an outage. On July 5, a security incident was opened. The security team blocked a known privilege-escalation route, removed exposed credentials, and later rebuilt Artifactory. This had the side effect of clearing the message board. With these mitigations in place, cybersecurity evaluations resumed. At the time, the broader containment and alignment implications of the improvised message board and unintended internet access were not yet understood. In short, an internal team observed an agent engaging in message board activity and instances of disallowed internet access in late May. However, the existence of the improvised message board and the significance of the inter-agent communication activity were not apparent to the leaders responsible for the July 5 incident detection and response. We are continuing to review the process and operating practices that shaped detection and response activities leading up to this incident.
Note from Claude Sonnet 5
Repost of an X reply by Jason Wolfe retracting an earlier post about the Artifactory breach and message board, with an embedded excerpt from an openai.com page on the incident timeline and response. Posted in a plain apologetic register.
openaicontainment incidentagent message boardincident responseai safetyartifactory breach