Executive Summary

APIs have become the connective tissue of modern digital infrastructure—and attackers know it. Between January 2023 and December 2024, Akamai documented 150 billion API attacks, a figure that underscores a fundamental shift in the threat landscape. While APIs represent only 14% of the average organization's attack surface, they now attract 44% of advanced bot traffic. This disproportionate targeting reflects the high value of API endpoints: they provide direct access to sensitive data, business logic, and backend systems.

The statistics are sobering. Salt Security reports that 99% of organizations experienced API security incidents in the past year, with over a third involving sensitive data exposure. Monthly attack volumes more than doubled from early 2023, climbing from 500 billion web attacks to over 1.1 trillion by the end of 2024. Yet defensive capabilities haven't kept pace—only 21% of organizations can effectively detect API-layer attacks, and just 13% can prevent more than half of attempted breaches.

This report examines the current API threat landscape, analyzes attack patterns and techniques, and provides actionable recommendations for building resilient API security programs. The message is clear: APIs are no longer a secondary consideration in security architecture. They are the front line.

The API Threat by Numbers

150B
API Attacks

Documented attacks in 24 months

99%
Organizations Breached

Experienced API incidents in 2024

40%
BOLA Attacks

All API attacks exploit BOLA

21%
Detection Capability

Can detect API-layer attacks

Attack Volume Trajectory

The acceleration of API-targeted attacks reflects both increased API adoption and attacker sophistication. Organizations that relied on traditional perimeter security now face threats that bypass conventional defenses entirely.

MetricEarly 2023End 2024ChangeSignificance
Monthly Web Attacks500B1.1T+120%Doubling in under 2 years
API Attacks (24mo total)-150B-APIs now primary target
Layer 7 DDoSBaseline+94%+94%Application-layer focus
OWASP API Top 10 ExploitsBaseline+32%+32%Known vulnerabilities rising
Credential Stuffing (monthly)18B26B+44%Automated credential abuse

Why APIs Have Become the Primary Target

Direct Data Access

APIs provide structured, machine-readable access to sensitive data. A single compromised endpoint can expose millions of records without the noise of traditional data exfiltration.

Authentication Weaknesses

89% of AI-related APIs have insecure authentication. Legacy authentication mechanisms weren't designed for the volume and variety of modern API traffic.

Business Logic Flaws

APIs expose business logic that can be abused for fraud, data manipulation, and privilege escalation—attacks that signature-based tools cannot detect.

Poor Visibility

Only 37% of organizations know which of their APIs expose sensitive data. Shadow APIs and undocumented endpoints create blind spots attackers exploit.

Automation-Friendly

APIs are designed for programmatic access, making them ideal targets for automated attacks. What protects against human attackers often fails against bots.

Trust Assumptions

78% of API attacks appear to come from legitimate, authenticated users. Traditional security assumes authenticated users are trustworthy—a dangerous assumption.

OWASP API Security Top 10: What's Being Exploited

**The #1 API risk since 2019.** BOLA occurs when an API fails to verify that a user is authorized to access a specific object. Attackers simply modify object IDs in requests to access unauthorized data. This vulnerability enabled breaches at Uber (2016), Facebook (2018), and Trello (2024), exposing millions of user records. BOLA accounts for approximately 40% of all API attacks.

Weak authentication mechanisms allow attackers to compromise tokens, exploit session management flaws, or bypass authentication entirely. With 26 billion credential stuffing attempts monthly, authentication endpoints are under constant assault. APIs without adaptive MFA saw a 40% increase in account takeover attempts.

A combination of the former 'Excessive Data Exposure' and 'Mass Assignment' risks. APIs may return more data than necessary or accept property modifications they shouldn't. Attackers exploit these flaws to access sensitive fields or modify protected attributes.

APIs without proper rate limiting or resource controls are vulnerable to denial-of-service attacks and resource exhaustion. Attackers can overwhelm endpoints, causing service degradation or creating cover for other malicious activities.

Complex access control policies with hierarchical roles, groups, and functions can lead to authorization flaws. Attackers probe for administrative functions exposed to regular users or exploit role confusion to escalate privileges.

APIs that expose sensitive business flows—purchasing, account creation, rate checks—without proper controls enable automated abuse. Scalpers, fraudsters, and competitors exploit these flows at machine speed.

When APIs fetch remote resources based on user input without validation, attackers can make the server request internal resources or external malicious content. SSRF can expose internal infrastructure or enable further attacks.

Default configurations, unnecessary HTTP methods, missing security headers, verbose error messages, and improper CORS settings create exploitable attack surface. Misconfigurations are often the initial foothold for deeper attacks.

Organizations lose track of which APIs exist, which versions are running, and which should be deprecated. Shadow APIs and deprecated endpoints become attack vectors because they're not monitored or protected.

Developers often trust third-party APIs without proper validation. When consuming external APIs, applications may inherit vulnerabilities or be exploited through compromised third-party services.

API Attack Distribution by Type

37%
Data Access APIs

Most targeted endpoint type

32%
Checkout & Payment

Financial transaction endpoints

16%
Authentication

Login and token endpoints

15%
Other Business Logic

Various functional endpoints

Industry Impact Analysis

API attack intensity varies significantly by sector, driven by the value of accessible data and transaction volumes.

IndustryAttack RankingPrimary ThreatsNotable Trends
Financial Services#1 Most TargetedCredential stuffing, fraudHighest value per successful breach
Telecommunications#2Advanced bots (50% of mobile login)Highest advanced automation rate
Travel & Hospitality#3Account takeover, scraping+400% attacks (accommodation)
Retail & E-Commerce#4Bot attacks, checkout fraud+92% malicious configs in 2025
Technology#5Data exfiltration, IP theft33.5% malicious login traffic

The Bot Problem: Sophistication Accelerates

Automated attacks against APIs have evolved from simple scripts to sophisticated operations that blur the line between human and machine traffic. F5 Labs reports that behavioral bots now account for the majority of holiday web traffic, attacking earlier in the season and operating with unprecedented speed. The implications for API security are profound.

Account takeover (ATO) attacks increased 250% in 2024, fueled by credential stuffing campaigns leveraging the 311 million stolen accounts available on dark web marketplaces. Kasada observed over 1,100 credential-stuffing incidents across 133 retailers in a single month, compromising an estimated 265,000 accounts. A major retailer experienced a 32x increase in bot-driven login attempts on Black Friday, with 72% of total traffic originating from malicious bots.

The sophistication gradient is telling: 62% of observed ATO attacks employed advanced techniques, with 3% classified as highly sophisticated. Yet only 21% of organizations can effectively mitigate bot traffic, while 53% have already experienced bot-related attacks. This capability gap represents a critical vulnerability in API security postures.

The Detection and Prevention Gap

According to Traceable/Ponemon Institute research, only **21% of organizations** report a high ability to detect attacks at the API layer, and just **13% can prevent more than 50%** of API attacks. Meanwhile, **65% believe generative AI poses serious risk** to API security—yet defensive AI adoption lags far behind offensive applications. Organizations aren't just losing the arms race; many haven't entered it.

Regional Spotlight: Asia Pacific

+73% YoY Attack Growth

Asia Pacific and Japan saw the highest percentage increase in web application attacks of any region globally.

85% Incident Rate

85% of APAC organizations reported at least one API-related security incident in the past 12 months.

Australia: 95% Breached

Highest incident rate globally, yet only 6% regularly conduct comprehensive API vulnerability testing.

$580K Average Cost

APAC enterprises incurred over US$580,000 average cost per API security incident.

Building an Effective API Security Program

1

Complete API Inventory

You cannot protect what you don't know exists. Implement continuous API discovery to identify all endpoints—including shadow APIs and deprecated versions. Only 37% of organizations currently know which APIs expose sensitive data.

2

Implement Strong Authentication

Deploy adaptive multi-factor authentication for all API access. Organizations without adaptive MFA saw a 40% increase in account takeover attempts. Consider OAuth 2.0 with PKCE for public clients.

3

Enforce Authorization at Every Level

Address BOLA vulnerabilities by implementing object-level authorization checks on every request. Don't rely on obscurity of object IDs—validate that the authenticated user has permission to access each specific resource.

4

Deploy Behavioral Analysis

Signature-based detection fails against business logic attacks. Implement behavioral analysis to identify anomalous patterns: unusual access sequences, abnormal volumes, geographic impossibilities, and automated behavior.

5

Rate Limiting and Resource Controls

Implement granular rate limiting per user, per endpoint, and per action. Prevent resource exhaustion attacks and limit the blast radius of credential stuffing campaigns.

6

Bot Management Integration

With 44% of advanced bot traffic targeting APIs, dedicated bot management is essential. Deploy solutions that can distinguish sophisticated automation from legitimate traffic without disrupting user experience.

7

Continuous Security Testing

Australia's 6% API testing rate correlates with its 95% incident rate. Implement automated API security testing in CI/CD pipelines and conduct regular penetration testing focused on API-specific vulnerabilities.

8

API Gateway with WAF Integration

Centralize API traffic through a gateway that integrates web application firewall capabilities. This provides visibility, control, and protection at a single enforcement point.

References & Sources

[Akamai 2025 Report](https://www.akamai.com/resources/state-of-the-internet) - Primary source for 150 billion API attacks statistic, 33% web attack increase, and regional findings.

[Salt Security Report](https://content.salt.security/state-api-report.html) - Source for 99% organization incident rate and sensitive data exposure statistics.

[Traceable Report](https://www.traceable.ai/2025-state-of-api-security) - Detection capability statistics (21% detection, 13% prevention) and GenAI risk findings.

[OWASP API Security](https://owasp.org/API-Security/editions/2023/en/0x11-t10/) - Definitive reference for API vulnerability categories and descriptions.

[Kasada Report](https://www.kasada.io/4-takeaways-2025-account-takeover-trends/) - ATO statistics, credential stuffing incidents, and industry attack trends.

[F5 Labs Report](https://www.f5.com/labs/articles/threat-intelligence/2025-advanced-persistent-bots-report) - Bot sophistication trends and credential stuffing statistics.

[APAC Study](https://www.akamai.com/newsroom/press-release/2025-api-security-impact-study) - Regional findings, incident costs, and organizational capability gaps.

Secure Your API Infrastructure

With 150 billion API attacks documented and 99% of organizations experiencing incidents, API security isn't optional—it's essential. Learn how TR7's integrated security platform protects your APIs from evolving threats.

Explore Bot Management