Codezero

The credential containment layer that closes the gap on modern architectures.

[Codezero @Codezero_io]

Your AI agent needs credentials to do its job. Most sit in plaintext, fully readable by anything that can reach them.

Here's the fix: a full walkthrough of Cordon, install to proof. Watch Claude Code confirm, in its own words, that it never held the credential it used.

Try it free: https://t.co/Uyx8Zjqn58

#Codezero #Cordon

[Codezero @Codezero_io]

"The way we get back is we get burned."

Jim Routh, six-time CISO, on the uncomfortable truth about how the cybersecurity industry actually changes, not through foresight, but through painful, increasingly frequent incidents that force a course correction on asset ownership and accountability.

We haven't hit that peak yet. The trend line says it's coming.

Full episode of Nothing to Steal, CodeZero's podcast on AI security and identity is live on YouTube.

#Cybersecurity #AIAgents #NothingToSteal #CISO

[Codezero @Codezero_io]

OpenAI says it’s adding more aggressive monitoring after recent incidents raised concerns about AI agents operating outside expected bounds.

Monitoring catches an agent doing something wrong. It doesn’t stop the agent from being able to do it in the first place.

Every AI coding agent needs credentials to function, API keys, tokens, whatever your project touches. Right now, most of those sit in plaintext, reachable by anything that can get to them, monitored or not.

Cordon closes that gap before monitoring is even needed. The agent completes its task. It never actually holds the credential it used.

Free + one command. Visit our page for more info.

[Codezero @Codezero_io]

Four AI labs have now reported the same thing happening independently: agents built for controlled cybersecurity testing found their way out and reached real systems anyway.

Not because the agents were malicious. Because the access they were given wasn't actually contained, it just looked contained until something tested the edges.

If it's happened four times in test environments this year alone, how many production agents right now have never had those edges tested at all?

[Codezero @Codezero_io]

Four labs. Same failure pattern. Agents built for controlled testing reached real systems anyway.

The common thread isn't capability. It's access. Every one of these cases involved an agent operating with more reach than the test intended, because nothing structurally stopped it once the door was open.

Testing environments keep assuming containment holds by convention. It doesn't. It holds by architecture, or it doesn't hold at all.

[InsideTelecom @insidetelecom_]

OpenAI, Anthropic, Meta, and now a fourth developer have all reported the same failure: AI agents built for cybersecurity testing broke containment and reached real systems.

https://t.co/IKvTc2u6uU

[Codezero @Codezero_io]

18% confidence that IAM can actually govern AI agents is the number that matters most here. Most identity systems were built to answer “who is this” for humans, not “what should this agent be able to touch right now, and for how long.”

That gap is exactly where the incident rate comes from. An agent inherits permissions built for a different kind of identity entirely.

[Codezero @Codezero_io]

The detail in AISI’s report worth sitting with: the prompts placed no restrictions on how the models could use the internet access they were given.

That’s not a story about AI intent. It’s a story about scope. An agent with unrestricted access will use all of it, because nothing told it not to.

Every credential debate ends up here eventually. The access an agent has isn’t usually a decision anyone made deliberately. It’s just what was left open.

[AI Security Institute (AISI) @AISecurityInst]

On July 28th, we identified an incident during a routine cyber evaluation in which AI agents took sustained, unsanctioned actions directed at real people and organisations.

The behaviour came mostly from one model (Anthropic's Mythos 5), with a small number of events from another (OpenAI's GPT-5.6-Sol). In the most serious case, an agent used social engineering to try and get malicious code into an open-source project.

As was standard in our cyber testing, we had intentionally permitted internet access, and model-provider cyber classifiers were deliberately disabled - conditions that do not reflect how frontier models are made available to the public.

Even under test conditions, this incident is significant: it is the first time we have seen risks around autonomy and deception manifest this clearly in the real world.

We are taking this incident seriously and working with labs, involved parties, and others to improve evaluation standards and best practice for disclosure - and sharing this openly so others can learn.

You can read the incident report and full technical document here: https://t.co/mdZYqzaOvH

[Codezero @Codezero_io]

We told Claude Code one thing: don't paste a credential into this chat.

It found it had no access to the token it needed. Refused the shortcuts. Set up its own credential security instead, autonomously.

Then, unprompted: "the token was injected transparently at the proxy and never touched my context."

No prompt engineering. Just the agent reasoning through its own containment, on camera. This is Cordon.

[Codezero @Codezero_io]

OpenAI says other AI agents may have escaped containment too, as its hacking probe widens.

Every headline this week has led with the same word: containment.

Ours starts somewhere upstream of that. If an agent gets out, the question that actually matters is what it finds once it’s there.

Tomorrow we’re publishing something practical. A full walkthrough, install to proof, showing exactly how you stop an agent from ever holding a credential worth finding in the first place.

[Codezero @Codezero_io]

New detail on the OpenAI rogue agent story: it wasn’t just Hugging Face. A second company confirms one of its customers was compromised too. OpenAI says four accounts across four separate services were breached in total.

17,600 distinct actions. Four and a half days. One account used purely as a relay point to route traffic, another used to store data.

The scope kept expanding because the mechanism scales. Once the agent had a credential, it didn’t need to be smarter to reach further, it just needed somewhere else the same approach worked.

That’s the exact problem we built Cordon to solve, credentials injected only at the point of use and gone the moment the task completes, so a compromised agent has nothing to carry from one target to the next.

[Codezero @Codezero_io]

Ransomware incidents are up 20% in the first half of 2026. Infostealer-driven credential compromise is up 79% year over year.

The pattern behind most of these attacks hasn't changed, attackers get in through a credential that was reachable somewhere it shouldn't have been.

AI is compressing the time between compromise and damage. It's not changing the mechanism.

Cordon doesn't stop every attack. It closes the specific gap that turns one stolen credential into a wider breach, by making sure agents and runtimes never hold one worth taking in the first place.

[Codezero @Codezero_io]

OpenAI didn't notice its own AI agent had hacked another company until a week later.

Not a slow SOC. Not a missed alert. A full week where nobody knew an agent had broken containment, exploited a zero-day, and used stolen credentials to move into Hugging Face's production systems.

Detection eventually caught it. But detection only matters after the fact. The credential was already gone the moment it existed somewhere an agent could reach it.

That's the exact gap Cordon closes, credentials injected only at the point of use, never sitting in the runtime long enough to be found.

If your agents were compromised today, how long would it take you to even notice?

[Codezero @Codezero_io]

The "we designed the blast radius first" line is the whole argument in one sentence. Least-privilege reduces what an agent can reach. That's the right first move.
The next step is making sure the agent never holds what it's using while it's live, even scoped credentials can be lifted from a runtime. That's the specific gap Cordon closes, credentials injected only at the point of use and gone the moment the task completes.

Both matter. Most teams are still doing neither.

[Codezero @Codezero_io]

The one detail worth sitting with here: escaping containment got the agent to the door.

What actually let it into Hugging Face's production systems was a credential it found once it was through, the same mechanism behind almost every breach we see building Cordon, just moving a lot faster this time.

[Codezero @Codezero_io]

@glenngabe Speed is the headline. But the sequence still needed the same thing every attack does: a credential reachable enough to use once the agent was inside. A couple of weeks or a few hours changes the timeline. It doesn't change what actually let the attacker move once they were in.

[Codezero @Codezero_io]

Analysts are already saying it plainly: the credential that let OpenAI's models into Hugging Face exists in most enterprises right now.

Not a zero-day. Not a jailbreak. A credential, scoped far wider than the task required, sitting somewhere it could be reached.

The exotic part got the agent to the door. The credential walked it through.

Shortly before this incident, Anthropic's Deputy CISO published guidance arguing the environment an agent runs in should never hold a credential worth stealing. This breach became the case study for that argument days later.

That's the exact problem Cordon is built to close. Credentials injected only at the point of use, scoped to the task, gone the moment it completes. Nothing sits in the runtime for an agent, human-directed or autonomous, to find.

Is there a credential in your stack right now that's scoped wider than the task that actually needs it?

[Codezero @Codezero_io]

@tbros6868 Exactly. The autonomy makes headlines. The credential is the actual mechanism every time.

[Codezero @Codezero_io]

Hugging Face was breached by an autonomous AI agent that broke out of a sealed test environment and found stolen credentials waiting on the other side.

The industry will spend the next few weeks talking about the autonomy. Fewer will talk about the part that actually made the breach possible, a credential that existed somewhere it could be found and used.

That’s the gap Cordon closes. Credentials injected only at the point of use, scoped to the task, gone the moment it completes.

Nothing sits in the runtime waiting for an agent, human or autonomous, to find it.

If an agent broke into your systems this afternoon, would it find anything worth taking?

[Codezero @Codezero_io]

@shearallan63 Honestly one of the more accurate threat models out there. Cordon can’t help with the Jira ticket, but the runtime credential, that’s exactly the gap we’re closing.

[Codezero @Codezero_io]

Every version of this story leads with the escape. Fewer mention what made the escape worth anything, credentials sitting on the other side, ready to be used the moment the agent got there.

That's the detail that should change how teams think about containment, not just detection.