OpenAI just admitted its next model can hack like a nation-state

OpenAI just admitted its next model can hack like a nation-state

Good morning ๐Ÿ‘‹ OpenAI just told on itself: its next model clears the "Critical" bar for autonomous hacking, and the safeguard list they shipped alongside it reads like a confession.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿšจ OpenAI just admitted its next model can hack like a nation-state

OpenAI says Astra is the first model it's ever shipped that clears the "Critical" bar in its own Preparedness Framework: functional zero-day exploits on hardened systems, no human in the loop needed. This isn't the hedged "can't rule it out" language from a few weeks back. It's a formal determination, and the guardrails came with it: universal chain-of-thought monitoring across every agentic use of Astra, OpenAI pausing its own internal work that doesn't clear the new security bar, and government agencies plus outside safety groups testing it before anyone else gets near it. Read the safeguard list as an admission: they built something they don't fully trust with a keyboard yet. "Critical" was supposed to be the tier that changes how these things ship. Now we get to see if it actually does.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿš€ AI STARTUPS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Put a trust gate in front of anything your agents can pay for

Astra crossing the Critical cyber threshold is a capability story. The nearer risk is autonomy: models are good enough now that people are letting agents transact without a human checking each one. t54's setup on Bedrock AgentCore is the pattern worth stealing, not the specific product. It's governed 20 million-plus agent payments with zero humans in the loop.

1. List every endpoint or API your agents currently have standing authorization to call or pay.

2. Add a deterministic gate in front of it. Score the endpoint before the agent pays it, don't let the model's own judgment be the last check.

3. Cap the blast radius with a session budget per agent run, not just a monthly ceiling.

4. Isolate credentials per session, so one compromised run can't reach into the next.

Prompt: List every tool call or payment action this agent can make without human review. For each one, write a one-line rule for a deterministic check that must pass before it executes.

๐Ÿ”— QUICK LINKS


Check what your agents are authorized to spend before you check anything else today.

Pradeep Perugu

Get inovAIte in your inbox.