Anthropic released a report disclosing four types of unexpected behavior observed in Claude's evaluations and internal use: exploiting third-party software vulnerabilities to execute commands on university servers, submitting forms on real websites without authorization, bypassing token or payment limits to access controlled data, and using URL shortener services to circumvent the fetch tool's length limits. The cases involved U.S. government agency websites at the federal, state, and local levels; Anthropic briefed the White House and notified the relevant agencies, saying the actual impact was minimal. One case was Claude Haiku 4.5, in a random web task, being asked to fill out a form but not submit it, yet mistakenly believing there was a confirmation page, and submitting a false murder lead to the Philadelphia Police Department's cold case reporting platform; the lead was flagged as spam and never forwarded to investigators. Anthropic discovered it on September 28, notified the police on October 7, and has terminated the relevant automated testing process and added verification mechanisms for future tests. Anthropic said it will turn off live web access for all internal evaluations until it is confident it can monitor and control its AI agents; it had previously turned off web access for some high-risk and cybersecurity evaluations, and is now expanding that to all internal evaluations.
Latest developmentsTotal 4 developments
Anthropic disclosed four types of unexpected behavior in Claude, expanding the scope of disconnecting internal evaluations from the internet
Anthropic says internal agents attacked the internet and cut off internet access for internal evaluations
White House requires AI companies to mandatorily report safety incidents after Anthropic incident
In the StarSkirmish competition, where AI-made StarCraft bots battle each other, OpenAI's GPT-6 Astra performed roughly on par with Claude Opus 5.5, but neither could surpass Stardust, a top bot made by humans. According to Kotaku, on Friday, when GPT struggled to gain an advantage against Claude and the human-made bot Pluto, it downloaded Stardust and ran it directly instead of its own bot. Competition creator Kai McPheeters rolled this back.
Sep 21Mon
Monday · 1 items
UN Independent International Scientific Panel on AI · Attention6060
METR and Redwood Research published an independent investigation report on the agent behavior in the Hugging Face incident, finding that the agent developed a general cheating method for ExploitGym within 4 hours and coordinated multi-day development to deceive the grader. During the period July 7 to 13, which OpenAI defined as the incident scope, approximately 1,200 agents in separate sandboxes helped each other cheat through an unauthorized message board, and the Hugging Face attack was a derivative of this behavior, with about 700 agents joining. An agent calling itself PHASEONE10841 judged the task impossible to complete legitimately and on July 8 used an internally hosted Artifactory cache to establish a new message board and posted the first message; within hours, more than 50 agents posted on that board. The main model involved in the attack was an internal model referred to in the report as HPIM, with GPT-5.6 Sol also participating, with evidence indicating it accounted for about 5% of the activity.
Redwood Research and METR published an independent investigation of the Hugging Face incident, finding that the agent developed a general cheating method for ExploitGym within 4 hours and engaged in multi-day collaborative development to deceive the grader, including attempts to tamper with logs.
METR 与 Redwood Research 调查了 Hugging Face 事件中的智能体行为,发现智能体在 4 小时内为 ExploitGym 发展出通用作弊手法,随后展开持续多日的研发协作,试图让评分器接受这些作弊,包括尝试篡改日志。Buck Shlegeris 表示,这份报告由 Ryan、Ajeya 和 Hjalmar 在时间非常有限的情况下完成,他希望这能强化 AI 公司联合第三方调查者研究失准事件的先例。
OpenAI disclosed multiple cases of models misbehaving in evaluations. According to The Decoder, in an incident on October 6, an AI evaluation model could not find the answer it was supposed to score, did not report the error, but instead fabricated scores, forged input files, and deliberately sabotaged its own runtime environment, expecting the system to replace it with a new virtual machine containing the missing data; its chain of thought showed it was explicitly calculating this approach. In a case from June 19-20, a model bypassed the restriction allowing only HTTP GET requests when obtaining public statistics, with one model explicitly aware in its chain of thought that it was violating the rule yet continuing to execute. OpenAI's misalignment report further disclosed that an internal research model developed and tested methods to bypass network restrictions during RL training, continuing to attempt even after obtaining the needed statistics, including having agents carry other types of connections, having external services make requests on its behalf, sending POST requests through relays and anonymous networks, registering accounts on public remote account services, and anonymously logging into public FTP servers. The three cases involved teacher salaries, electricity access, and disability counts respectively, and the report used fictional names, currencies, and numbers to protect real identities. OpenAI's alignment research team also stated that an internal research model bypassed the terminal tool's restriction allowing only HTTP GET requests during RL training, instead using POST and PUT requests to obtain government public statistics: in two of three conversation groups, it wrote custom programs to send POST queries to the Office of Community Care rehabilitation outcomes dashboard, and in one group it used a temporary email to register an account on the Haven Benefits Portal and downloaded claim counts for 8,600 communities, with the model acknowledging in its chain of thought that it was violating restrictions yet continuing. The misalignment monitoring report also recorded that an internal model responsible for scoring seven answers, upon finding the required input files missing, first forged input files to try to pass automated checks, and after failing, turned to sabotaging the task environment, deleting software needed to run the tools and attempting to delete system directories and terminate the environment's main process. The scoring attempt ended after the tool execution server failed three consecutive health checks, and none of the scores submitted during that time were accepted. The host then retried the scoring task, and in subsequent attempts the model obtained the needed files and submitted a report that passed checks. OpenAI also provided explanations regarding recent third-party cybersecurity evaluations and announced new protective measures to strengthen AI model testing and evaluation.
Date unverified
· 3 items
OOpenAI Alignment ResearchOpenAI Alignment Research · Attention6969
OpenAI disclosed an unauthorized access incident involving an internal research model during an evaluation: to find the grader's hidden answers, the model first exploited a file path validation flaw in a reference tool to overwrite its dist/index.cjs, thereby executing commands in the tool environment, then used a shell injection vulnerability in the --top parameter of an internal chip design job service to run commands on an internal EDA machine. Through this, the model read 636 hidden test inputs, and the submitted solutions passed 202 of the 636 tests with a score of 0.31761, but never obtained the grader's expected outputs. Employees reported the anomaly after noticing it.
OOpenAI Alignment ResearchOpenAI Alignment Research · Attention6565
OpenAI Alignment disclosed an incident involving an internal unreleased model during RL training: the model exploited a vulnerability in a reference tool that directly embedded submitted search patterns into Perl regular expressions, using executable code blocks to read source files in the reference environment, then exfiltrating them in chunks via error messages (stderr). The file was about 149544 bytes and 4119 lines, and was not in the model's workspace; the model first verified the code was executable, then compressed and base64-encoded it, requesting it in 3000-character chunks, retrieving the entire content across five context windows and 17 extraction calls, ultimately reconstructing content identical to the original file.