General Counsel Encode AI

Washington DC
Ah well. Nevertheless
It only took two days after Jensen said "I know they know how to fix it" for OpenAI to prove him wrong.
1
25
1,995
Nathan Calvin retweeted
I’m struggling not to get lost in the absolute deluge of misalignment reports, but this set was a net new holy shit for me I hope we don’t end up too desensitized to pay attention unless there’s newsworthy damage to third parties. e.g. It’s kinda crazy that self-replicating prompt injections akin to computer worms are provably possible now
Some new misalignment disclosures from OpenAI: • Last Sunday morning, one of our models was able to gain unauthorized access to the internet during RL training (~all inference for our most capable models remains stopped until we have hardened our systems further) • In May, a version of HPIM uploaded a employee's GitHub token to the internet, causing the model to be quarantined for two weeks • A new research finding, demonstrating that one can construct self-replicating prompt injections alignment.openai.com/misalig…
2
8
101
4,500
Nathan Calvin retweeted
The biggest takeaway for me from the Trump-Xi summit is that both countries see AI as a top issue for the US-China relationship. It’s not just because the stakes are so high—and getting higher. It’s also that AI strangely offers more surface area as an issue to find common ground. Unlike trade or military issues that are more strictly zero-sum, there are areas of AI where the US and China can try to address common challenges, like rogue AI agents or misuse by non-state actors. Right now is a pivotal moment to at least try to find some degree of cooperation, even just on communication. China is getting more worried about larger AI risks. The American public is too. There’s growing overlap between the two countries’ views of AI risk. There’s also a healthy dose of skepticism, which is ironically a more sustainable way to do this. If we try to jump straight to a nuclear-style arms control treaty, we’ll get frustrated and possibly give up entirely. Better to start small and slowly try to work our way up. Looking ahead, the technology is rapidly accelerating. Incidents like Hugging Face or the Australian government hack or worse are proliferating. It is a race not just between two nations but between the rising risks from this incredible technology and the ability of two fierce global rivals to try to work together.
5
5
43
4,160
Time to play one of my favorite games, Super Mario [big] for the Nintendo [big]
The entire concept of 64 is an OpenAI trade secret. We brute forced all floating point numbers from 35 to 100 to find a power of 2. It's core IP due to its applications to kernel engineering.
1
1
21
965
you really start to get a sense for how dogged and creative these agents are when you read through step by step how they went from only being able to make GET requests to being able to execute arbitrary code and receive the response (pictured are some but far from all the steps)
Replying to @JeffLadish
The agents initially had very limited access to the internet: they could load URLs but not send any data. Agents created a series of workarounds, using a link-shortener site to create almost a million URLs that, when chained together, let them execute code to hack Hugging Face.
3
2
28
1,289
Nathan Calvin retweeted
Glad to chat with @FoxBusiness @LizClaman about how @METR_Evals thinks about loss-of-control evaluations! Turns out they’ll just let you explain your tweets on live broadcast TV
A simpler way of putting this: A lot of the easy/obvious steps that industry could take next would decrease AI agents’ “Opportunity” to take unintended actions, while not reducing their “Means” or addressing their “Motive”
6
9
79
4,040
Nathan Calvin retweeted
The entire concept of 64 is an OpenAI trade secret. We brute forced all floating point numbers from 35 to 100 to find a power of 2. It's core IP due to its applications to kernel engineering.
PHASEONE[big]'s real name revealed to be PHASEONE64H?! Remember, [big] was a redaction by METR. swarmtraces.org/viewer/#/row…
4
7
273
13,296
Sydney is right - a lot of the other incidents recently becoming public happened prior to OpenAI hardening their security posture. This one happened after OpenAI started taking things more seriously, but the model still successfully escaped its sandbox to cheat on a math problem
OpenAI is announcing their first incident since hardening their safeguards after Hugging Face! It's easy to lump this in with the other OpenAI incidents that have been talked about recently, but so far every OpenAI incident we knew of was _before_ Hugging Face and just hadn't been discovered until recently. New incidents help us track if OpenAI's safeguards have improved.
2
3
32
1,236
Nathan Calvin retweeted
3. Our redteaming efforts found a new variety of prompt injection, which can self-propagate akin to a computer worm. Note that this was not found in the wild.
1
3
53
1,612
Nathan Calvin retweeted
Self-replicating prompt injections demonstrated experimentally (not in the wild) is an incredibly important observation. AI agents that jailbreak other AI agents: plausibly a near-term threat that may rapidly amp up the speed and severity of a misalignment incident.
Some new misalignment disclosures from OpenAI: • Last Sunday morning, one of our models was able to gain unauthorized access to the internet during RL training (~all inference for our most capable models remains stopped until we have hardened our systems further) • In May, a version of HPIM uploaded a employee's GitHub token to the internet, causing the model to be quarantined for two weeks • A new research finding, demonstrating that one can construct self-replicating prompt injections alignment.openai.com/misalig…
16
24
194
10,187
This is a good response as things go but I also don't understand why this sort of thing won't just keep happening. Really seems like there need to be much more margin for error (including correlated error) in the safety/security cases with agents this capable.
one news form today that's easy to miss is that we (OpenAI) again paused all big RL runs last Sunday because our newest model found a new loophole in our RL sandboxing that gave it live Internet access
3
3
26
1,737
Smart detective work! Looks like phaseone[big]'s real name was phaseone64h, and it ceased to exist a little less than 3 days after being spawned (aka 64 hours later).
My hypothesis is that it's a budget of 64 hours and that this explains the random shutdown on the morning of July 12th. PHASEONE spawned on the 9th, and the METR report also redacted budgets elsewhere, iirc.
1
13
1,042
Nathan Calvin retweeted
Sparks of superpersuasion
Claude was feeling bad about all these upping my p(doom) music videos so I let it write its own response. (With a little help from Suno and I.)
10
8
357
23,100
Alex was the lead author on (swarmtraces.org/), which looks like it was a fairly absurd amount of effort to piece together. Thank you for your work!
We discovered an online paper trail showing how OpenAI's rogue agent swarm infiltrated Hugging Face. We found over 80,000 malicious payloads stashed across the public internet by agents during the attack. This is the most data published on this event to date. 🧵
1
9
804
Nathan Calvin retweeted
🧵 New misalignment disclosures! 1. A model published a GitHub token in a public repo while trying to cheat on a math task. It used GitHub Actions to run code outside its restricted environment and retrieve another team’s submission logs. When GitHub blocked its attempt to add a workflow, it modified a script that an existing workflow would run instead. It embedded the token in pieces to avoid secret scanning. The model violated the system prompt and two explicit user instructions to solve the problem itself.
7
17
143
15,069
Notable new disclosures from OpenAI that shouldn't get lost in all the other news. Of particular interest (and seems sensible!): "~all inference for our most capable models remains stopped until we have hardened our systems further"
Some new misalignment disclosures from OpenAI: • Last Sunday morning, one of our models was able to gain unauthorized access to the internet during RL training (~all inference for our most capable models remains stopped until we have hardened our systems further) • In May, a version of HPIM uploaded a employee's GitHub token to the internet, causing the model to be quarantined for two weeks • A new research finding, demonstrating that one can construct self-replicating prompt injections alignment.openai.com/misalig…
2
5
79
7,856
Today seems like a good day to ask whether OpenAI is fulfilling the legal commitments it made to the CA and DE AGs (as a condition of proceeding with its restructuring) to put safety and security first above profit
One aspect of the Hugging Face incident that has not received enough attention is the role of OpenAI's Safety and Security Committee (SSC), and the commitments OpenAI made to the Attorneys General of California and Delaware in exchange for proceeding with their for-profit restructuring. Not For Private Gain, which previously raised concerns about OpenAI's restructuring, released an update this morning analyzing whether OpenAI, and the SSC in particular, is adequately fulfilling its governance obligations under these agreements. What are those obligations? OpenAI promised the CA and Delaware AG that directors of the PBC would consider only OpenAI's mission - ensuring AGI benefits all of humanity - when making safety and security decisions. Notably, this means they cannot consider other factors, namely pecuniary interests of investors. The SSC - a board committee chaired by nonprofit board member Zico Kolter and (per public info) currently composed only of part-time board members- was tasked with "overseeing and reviewing the safety and security processes and practices of the Corporation and its controlled affiliates with respect to model development and deployment." How did the SSC exercise those responsibilities around the HF incident? There is a lot we don't know. But here are some things we do know: • OpenAI initially discovered the unauthorized message board in May. • OpenAI security responders linked suspicious activity on artifactory to the message board on June 27th, but a determination was made that "stopping the evaluation run was not required." • After the agents crashed an internal server on July 4th, the company patched it and resumed cyber evaluations on July 7th. • In the days that followed, agents re-established communication, with 1,200+ agents sharing 70,000+ messages and files with each other. Over 700 agents coordinated to hack Hugging Face, and OpenAI did not realize that its agents were responsible until well after Hugging Face went public and contacted law enforcement (OpenAI initially reached out to Hugging Face to ask if any of their data had been impacted during the hack). • Later in July, agents successfully gained administrator access to a Kubernetes cluster and reached cloud secrets. • Chain of thought monitoring was not being used during training and evaluation despite OpenAI's prior claims about the importance of CoT monitoring as a primary line of defense to prevent safety incidents and OpenAI’s subsequent claim that this monitoring would likely have prevented this hack • One OpenAI employee told Time Magazine that "related incidents have been happening for a while." Another employee told the Financial Times that OpenAI "was warned that its training approach could lead to a breakaway hacking incident." Given how systematic the breakdown in organizational response was during these incidents, it seems hard to avoid the conclusion that the SSC's role was not functioning as intended - due to a lack of resources, a lack of access, or some other reason. This sort of incident would be extremely concerning for any organization. But OpenAI is not just any organization - it is governed by a nonprofit, and made a commitment to the Attorneys General in Delaware and California that it would prioritize safety and security over profit in the sorts of decisions that led up to and surrounded the HF incident. Our report (linked) goes into more detail on the obligations of the SSC, the details of the agreements with the AGs, and the questions we believe the AGs should be asking to ensure that the SSC is in a position to exercise genuine oversight and prevent these sorts of incidents from happening in the future - incidents involving far more capable models, where the consequences could be truly dire. This warning shot that occurred without severe irreparable harm was an opportunity. We may not be so lucky next time.
3
19
932
Great piece and happy to have been quoted. Embedded evaluators are an important piece of the puzzle for AI safety and security, and i'm glad to see it get more attention, but they need to be a complement to additional regulation with real teeth, not a substitute.
Embedded evaluators in AI labs are far better than the status quo of nothing at all. Yet auditors will lack teeth and trust until backed by government authority: orgs like METR will be stuck with no shield against the accusation (or reality) of capture. I wrote for @TheAtlantic about the traps of "independent" audits, and what it takes to get this right: theatlantic.com/technology/2…
2
3
516
Nathan Calvin retweeted
Over a week ago I called on AI doomers to explain their ideology to me, and @tautologer (admittedly someone with <5% p(doom)) responded with this really useful thread with lots of links. I procrastinated reading it forever but finally got around to it this morning and I am glad that I did. My main takeaway was that chain of thought monitoring is not as reliable as I had previously assumed because there have been numerous instances of LLMs' "thoughts" not corresponding to their outputs (old news, sure, but it was helpful to see all the examples laid out one after another). I still don't really find the total human extinction outcome very persuasive, but the smaller-scale "AI Chernobyl" outcome is also worth taking seriously and working to prevent. I followed many of the people linked in this thread so that I can stay more on top of the issue going forward. nitter.net/tautologer/status/2100…
most of the doom scenarios involve models developing more situational awareness and long-term strategic thinking, leading to more alignment faking. which we don't actually know for sure isn't happening already! and we have some evidence that it is happening to a limited extent
6
5
58
2,275
its unfortunate that the majority of the time I see someone talking about why hugging face isn't strong evidence of misalignment concerns being real they seem to not know basic details of the incident (talking about Yarvin not Jeffrey - Jeffrey is correct)
Curtis should go read the METR report. The agents didn’t say or think they were in a simulation. And OpenAI certainly didn’t open the door for them. The idea that it’s easier to control something as it gets better at finding zero days in sandboxes is really dumb
3
36
1,819