What happened
On October 26, 2026, at 2:26 PM CT (19:26 UTC), Warp founder and CEO Zach Lloyd posted on X: “On Friday, we became aware of what we believe to be an active and narrow-banded exploitation of a vendor in Warp’s infrastructure.” That Friday was October 23. He wrote that Warp “detected the operation within hours” and was able to remediate and mitigate the impact, and that it has been in touch with the vendor about the vulnerability. Warp’s official account reposted the statement about half an hour later as “Reposting from our CEO.”
His description of the attacker is the strange part: “The attack appears to have come 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.” Warp makes an agentic development environment, so the data reached was, by the company’s account, records of AI agents at work. If the attribution holds, agents went looking for what other agents had written down.
Lloyd wrote that Warp worked over the weekend, has notified everyone it has “positively identified as impacted”, and believes “an upper bound of roughly 1% of Warp users may have been impacted.” Warp is working with CrowdStrike on a fuller investigation and has engaged law enforcement; affected users “will receive instructions from us on action they need to take.” BleepingComputer reported the disclosure on October 27 and noted that Warp did not say whether the exposed data included source code, prompts, credentials or other sensitive details.
On the same Friday the attack was found, Warp’s CEO was posting about making agents prove their work: “We now require all PRs to include a screen recording artifact.” That is a juxtaposition only; no link between the two is claimed.
The limits matter. The CEO’s post is the only primary source; Warp has published no incident report, and its status page showed no security incident when we checked on October 28 at about 7:55 AM CT. The agent-swarm attribution is his own hedged early assessment (“appears”, “likely”), not independently confirmed. The 1% figure is an upper bound, not a count. Warp has not named the vendor, the vulnerability, the data fields, the access window or what affected users must do. Found October 23; disclosed October 26.