Warp, the company behind the AI-powered Warp terminal and agentic development platform, says attackers exploited one of its vendors and reached “a limited amount of agent trace and telemetry data” belonging to its users. CEO Zach Lloyd said the company’s early assessment points to “an agent swarm,” a coordinated group of automated AI agents, as the source of the attack.
Lloyd disclosed the incident in a statement posted on X on October 26, 2026, which the company’s official account reposted. He said Warp believes an upper bound of roughly 1% of its users may have been impacted. Warp’s website says the product is used by more than 800,000 developers, but the company has not said how many accounts the 1% figure represents.
On Friday, we became aware of what we believe to be an active and narrow-banded exploitation of a vendor in Warp's infrastructure. We detected the operation within hours and were able to remediate and mitigate the impact. We have been in touch with the vendor about the…
— Zach Lloyd (@zachlloydtweets) October 26, 2026
Warp detected the vendor exploitation within hours
According to Lloyd, Warp became aware on Friday, October 23, of what it believes was “an active and narrow-banded exploitation of a vendor in Warp’s infrastructure.” He said the company detected the operation within hours and was able to remediate and mitigate the impact.
Warp has been in touch with the vendor about the vulnerability. The company has not named the vendor, the affected product or the flaw itself, and no CVE has been linked to the incident publicly.
What Warp says the attackers reached
Lloyd described the attack as coming from “an agent swarm using a very sophisticated penetration and escalation technique, likely starting with a hole in a vendor dependency, and ultimately accessing a limited amount of agent trace and telemetry data.”
The wording matters. Warp says the attack “appears” to have come from an agent swarm and “likely” began with a vendor dependency. Both points reflect the company’s initial view, and no outside party has independently confirmed how the attackers got in or whether AI agents carried out the intrusion.
Agent traces are records of what an AI coding agent was asked to do and what it did, including steps taken and commands run. In a developer tool, that kind of record can reveal details about projects, internal systems and workflows. Warp has not said which fields the exposed traces and telemetry contained, or whether they included:
- Source code or file paths from user projects
- Prompts or full agent conversations
- API keys, tokens or other credentials that appeared in agent sessions
- Account details such as email addresses
The absence of that detail does not mean those items were affected, and it does not rule them out either.
CrowdStrike and law enforcement brought in
Lloyd said Warp staff worked through the weekend and have notified everyone the company has “positively identified as impacted.” Warp is working with CrowdStrike on “a more extensive and comprehensive investigation” and has engaged law enforcement.
“Everyone who uses Warp places a lot of trust in us and that’s not something we take lightly. I’m very sorry that this incident has occurred,” Lloyd wrote. He added that impacted users will receive instructions on actions they need to take and that Warp will post updates as it learns more.
As of publication, Warp had not published a detailed incident report, and its status page did not list the incident. It is unclear whether the unnamed vendor has notified its other customers.
Another AI developer tool hit through its supply chain
The Warp incident adds to a run of attacks on platforms that sit close to developer secrets and AI workloads. Earlier this month, BreachNews reported that Railway confirmed an attacker decrypted customer secrets while hunting for AI API keys, and that Zeabur is shutting down after a cyberattack exposed 3.2 million secrets.
Security researchers have long warned that AI coding agents collect rich context as they work. Logs of agent activity can capture terminal output, environment details and, in some cases, secrets pasted into a session. That makes the telemetry and trace pipelines behind these tools an attractive target, especially when they run through third-party services.
Steps for Warp users
Users who received a notice from Warp should follow its instructions first. Other users can take a few precautions while the investigation continues:
- Rotate any API keys, tokens or passwords that were typed, pasted or printed in a Warp agent session
- Review account activity on connected services such as GitHub, cloud providers and AI model providers
- Treat unexpected emails or messages that claim to come from Warp with caution, and verify them through
warp.devdirectly - Watch Warp’s official channels for updates on the vendor, the data fields involved and any further remediation steps
BreachNews will update this story if Warp names the vendor or shares more about the data exposed.
