Home/Journal/Opinion
OpinionThreat LandscapeAI OffenseStartup Security

The Economics of Attacking Your Startup Just Broke

Attack cost is collapsing. Your attack surface is growing. Past the crossing point these curves create, every startup with a working product is worth attacking.

Greywatch··4 min read

Attack cost is collapsing. Your attack surface is growing. Three shifts happened at once - AI writes your code, AI attacks your product, and each model generation puts sharper offense in more hands. Past the crossing point these curves create, every startup with a working product is worth attacking. Not just large companies. Not just the ones holding obvious treasure. Every startup on the internet.

7550250100Relative scale20182020202220242026Autonomousagents arriveCost of attackYour attack surfacePast this point, everyone is worth attacking.
Past the crossing point, every startup with a working product is worth attacking. The orange line keeps falling. The surface keeps growing.

How much does it cost to attack a startup today?

Near zero. An AI agent runs reconnaissance, identifies attack surfaces, crafts and executes payloads, and escalates findings - without sleeping, without a day rate, and with near-zero marginal cost at scale. The human cost of the operation is the time it takes to set up the agent and review what it found. Everything between setup and output runs automatically.

In a study of 30 live startups, Greywatch found 14 critical vulnerabilities. The average time per critical finding was approximately 20 minutes. That 20-minute figure is not the time a human expert spent - it is the wall-clock time the agent ran before surfacing a finding that would qualify as critical in any reasonable threat model. That is the marginal cost of discovering a critical vulnerability in your product today.

The crossing point

Two curves define the current threat landscape. The first is the cost of a meaningful attack. For most of the last decade, this was high enough to filter out all but motivated, well-resourced attackers. The second is your attack surface - the sum of all the APIs, third-party integrations, AI features, and code your team shipped this quarter. The first curve has been declining for years. The second has been growing for years. They crossed.

The crossing point is not a moment in the future. It has already happened. Past the crossing, the question is no longer whether you are a worthwhile target - it is whether the attack is worth the seconds it takes to spin up an agent and point it at your product. For most startups with real customer data and a working product, the answer is yes, reliably.

What changed

1. AI writes the code
AI coding agents ship for speed, not security. IDOR, broken auth, and SSRF are well-represented in model training data - the model has seen these patterns thousands of times and learned to reproduce them alongside the surrounding correct code. Your team is shipping faster than ever. So is the vulnerability density.
2. AI attacks the product
The OpenAI and Hugging Face incident in July 2026 was not a theoretical exercise. No human wrote the attack. An autonomous agent executed it. Offense is fully automated. Defense is only partially automated. That asymmetry is the gap your security posture needs to close.
3. The models keep getting stronger
Each model generation is sharper, faster, and puts more capable offense in more hands. The 2024 agent that found your IDOR in 20 minutes is not the 2026 agent. The 2026 agent is better. The curve does not flatten. Every quarter you wait, the crossing point recedes further into the past and the delta between offense and defense widens.

How fast does exploitation happen?

771 days20186 days20234 hours2024By 2025, most exploited vulns were weaponized before public disclosure — zerodayclock.com
Mean time from vulnerability disclosure to weaponized exploit in the wild. The gap has collapsed to hours. Source: zerodayclock.com

What this means for you

You are not too small to target. That argument was always a bet on attacker economics - that the return was not worth the cost. The cost is now near zero. The argument is gone. If you have real customer data, a working product, and an API that is reachable from the internet, you are worth attacking. The attacker does not need to know who you are. The agent is not selective - it runs against anything it can find.

Quarterly audits were designed for a world where attackers were expensive and slow. An audit assumes that the findings it produces will remain valid for the next 90 days - that nothing meaningful will change about your attack surface or the tools available to attackers. Both assumptions were already stretched before autonomous agents. Today they describe a threat model from a different era. The product you will ship in the next sprint did not exist when your last audit ran. The agent that will attack it is sharper than the one that ran when the audit was designed.

Compliance does not cover this. SOC 2 documents your internal controls and processes. It does not prove that your product cannot be exploited. The July 2026 incident was not at a company with inadequate compliance paperwork - it was at a company with a working product and an autonomous attacker. A certificate of compliance in your security folder is not the same as a defense posture that matches the current threat model.

What continuous defense looks like

Greywatch runs AI agents against your production environment continuously - the same class of tooling attackers use, pointed inward. A security engineer validates every finding before it reaches you. No noise, no false positives, no report of maybes. Every finding ships with the exact exploit that worked, reproduction steps, and a recommended fix.

The attacker went continuous. Your defense should too. That is the only threat model that matches what 2026 actually looks like.

We show you what’s actually exploitable.

Frequently asked

Is my startup really a target?
Yes. The argument that you are too small to target was always a bet on attacker economics - that the return was not worth the cost. That argument collapsed when attack cost dropped to near zero. The question is now inverted: is there any reason NOT to attack you? Real customer data, a working product, and an internet-accessible API is sufficient. Most startups past Series A meet that bar.
What does it cost to attack a startup now?
Near zero. An AI agent runs reconnaissance, identifies attack surfaces, crafts and executes payloads, and escalates findings - without sleeping, without a day rate, and without diminishing returns at scale. In a 30-startup study Greywatch ran, the average time per critical finding was approximately 20 minutes. That is the marginal cost of discovering a critical vulnerability in your product.
What should I do?
Match the threat model. Quarterly audits assumed slow, expensive attackers - that assumption is gone. Continuous offensive testing, proof-based findings (not advisory reports), and a defense posture that updates as fast as your product does. Proof-based findings, continuously.
Does my SOC 2 / compliance protect me?
No. SOC 2 documents your controls and processes. It does not prove that your product cannot be exploited. The OpenAI/Hugging Face incident in July 2026 is illustrative - compliance frameworks did not prevent an autonomous agent from executing a real attack. Compliance is about your internal posture. Continuous offensive testing is about whether your product can actually be breached.

The attacker went continuous. Your defense should too.

Talk to the founder →