LIVE LOG · entries last verified against sources between October 14 and November 6, 2026 · site updated Nov 6, 2026, 2:19 PM ET

← All incidents

Warp says an attack that exploited one of its vendors reached a limited amount of agent trace and telemetry data for up to roughly 1% of users

Incident · Warp (agentic development environment and terminal): agent trace and telemetry data · MEDIUM

Incident dateWarp became aware on Friday, Oct 23, 2026, per CEO Zach Lloyd. Warp has not said when the attack began.
DisclosedOct 26, 2026 (Lloyd's post on X at 3:26 p.m. ET; @warpdotdev reposted it at 3:34 p.m. ET and quote-posted it at 3:57 p.m. ET).
Added hereOct 28, 9:00 AM ET
Last verifiedOct 28, 2026

Summary

Warp, the terminal and AI coding-agent app, says an attack that exploited one of its vendors reached some user data. In a post on X on Oct 26, 2026, which Warp's official account reposted, CEO Zach Lloyd wrote that on Friday (Oct 23) Warp "became aware of what we believe to be an active and narrow-banded exploitation of a vendor in Warp's infrastructure", and that "We detected the operation within hours and were able to remediate and mitigate the impact." He wrote that the attack ended up "accessing a limited amount of agent trace and telemetry data", and that "we believe an upper bound of roughly 1% of Warp users may have been impacted." Warp says it has notified everyone it has positively identified as impacted, is working with CrowdStrike on a fuller investigation and has engaged law enforcement. Lloyd wrote that the attack "appears to have come from an agent swarm". That is Warp's early view. Warp has not said whether it has been confirmed, and we found no outside confirmation. Warp has not named the vendor, has not said what the traces and telemetry contained, including whether they held code, prompts or credentials, and has not said how many people the 1% covers. Warp's website says it is trusted by more than 800,000 developers. BleepingComputer and TSN reported the disclosure on Oct 27.

Severity

MEDIUM Medium (VibeIncidents editorial rating). Warp says an attack reached agent trace and telemetry data and that it has notified users it positively identified as impacted. We have not rated it higher because Warp describes the data as "a limited amount", puts the upper bound at roughly 1% of users, and says it detected the operation within hours and was able to remediate it. Warp has not said what the traces contained, so we may raise the rating if it turns out they held code, prompts or credentials.

Kit, our email provider, gets your address only to send the newsletter. Every email has an unsubscribe link. Privacy policy.

Timeline

  1. Oct 23, 2026 (Friday)
    Warp becomes aware of "an active and narrow-banded exploitation of a vendor in Warp's infrastructure", per CEO Zach Lloyd's Oct 26 post, which says this happened "On Friday". Lloyd says Warp detected the operation within hours. Warp has not said when the attack began.
  2. Oct 24 to 25, 2026 (weekend)
    Lloyd says Warp was "working over the weekend". By the time of his Oct 26 post, he says, Warp had notified everyone it had positively identified as impacted.
  3. Oct 26, 2026, 3:26 p.m. ET
    Lloyd posts the disclosure on X: a limited amount of agent trace and telemetry data accessed, an upper bound of roughly 1% of Warp users, CrowdStrike brought in and law enforcement engaged.
  4. Oct 26, 2026, 3:57 p.m. ET
    Warp's official account (@warpdotdev) quote-posts it: "Reposting from our CEO".
  5. Oct 27, 2026
    BleepingComputer and TSN report the disclosure. Neither adds new details about the incident from Warp beyond the post.

How it happened

Everything known comes from Lloyd's post. He wrote: "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." The words "appears" and "likely" are Warp's. Warp says it has been in touch with the vendor about the vulnerability and is working with CrowdStrike on "a more extensive and comprehensive investigation". Warp has not disclosed the vendor's name or the vulnerability. It has not said what the agent traces and telemetry contained, including whether they held source code, prompts, command output or credentials. It has not said whether the "agent swarm" attribution has been confirmed, how it was reached, or how many users the 1% upper bound covers. Lloyd wrote that anyone impacted "will receive instructions from us on action they need to take", but Warp has not published those instructions. We won't guess at any of these details, and we will update this entry when Warp publishes them.

How to check your app

Sources

Corrections and updates

None. Re-checked against every source on Oct 28, 2026.

Cite this entry
Title
Warp says an attack that exploited one of its vendors reached a limited amount of agent trace and telemetry data for up to roughly 1% of users
Added
Oct 28, 2026
URL
https://vibeincidents.com/incidents/warp-vendor-breach-agent-trace-telemetry-2026-10/
Suggested citation
VibeIncidents. "Warp says an attack that exploited one of its vendors reached a limited amount of agent trace and telemetry data for up to roughly 1% of users." Oct 28, 2026. https://vibeincidents.com/incidents/warp-vendor-breach-agent-trace-telemetry-2026-10/