Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Automatic API Attack Tool

github.com

  • Free plan
  • Windows
  • Linux
7.5 Club score Visit github.com

What Automatic API Attack Tool is

Automatic API Attack Tool is a free, self-hosted tool that takes an API specification and generates and runs security tests. It requires Swagger 2.0 in JSON or YAML. Its fuzzing scenarios send generated values that fit the specification as well as values that violate it, including random invalid values for checked parameters. The project says its request generation can be extended for attack types such as illegal resource access, XSS, SQL injection, and RFI. It supports authorization and input-validation testing, but does not discover APIs.

The tool prints request details, checks whether responses match expected results, and provides a summary. It writes TestNG results under build/testng-results and saves bad requests in a bad_requests folder. Optional host and port arguments can route requests through a proxy. The project describes running it in a Jenkins job triggered by a schedule or code push. It runs on Windows and Linux and requires Java 8 or higher and Gradle. The README recommends precisely defining legitimate response codes for endpoints and lists an MIT license.

Who it suits

It suits developers or security teams with a Swagger 2.0 API specification who want to run API fuzzing in a self-hosted CI/CD workflow. Users need Java 8 or higher and Gradle.

Good to know, and what to watch

  • Generates valid and invalid parameter scenarios
  • Supports authorization and input-validation testing
  • Can run in a Jenkins job
  • Optional proxy routing
  • MIT-licensed and free
  • Requires Swagger 2.0 specifications
  • Does not discover APIs
  • Requires Java 8 or higher and Gradle

MIT-licensed open-source tool

Free

Open source

The verdict

Automatic API Attack Tool offers specification-driven fuzzing for teams comfortable building and running a self-hosted project. Its Swagger 2.0 requirement and response-code setup deserve attention before use.

What the maker publishes

API format
The required specification is Swagger 2.0 in JSON or YAML format. source
Attack generation
It creates fuzzing scenarios by sending generated values within and outside the boundaries defined in the API specification. source
Attack vectors
The README says the tool can be extended to run attacks such as illegal resource access, XSS, SQL injection, and RFI. source
CI/CD
The project says it was built with CI/CD in mind and describes running it in a Jenkins job triggered by a schedule or code push. source
Extensibility
The project says its fuzzing and request generation functionality can be extended for specific needs. source
Fuzzing
It creates positive and negative fuzzing scenarios using generated parameter values that follow or violate the API specification. source
License
The repository lists an MIT license. source
Limits
The README says the required API specification must be Swagger 2.0 and recommends precisely defining legitimate response codes for endpoints. source
Linux
The README describes combining a runnable shell script with the JAR to make a Linux executable. source
Proxy support
Optional arguments let users route requests through a proxy by specifying its host and port. source
Purpose
The tool takes an API specification as input and generates and runs attacks based on it. source
Reporting
The tool writes TestNG results under `build/testng-results`, prints check details and a summary, and stores bad requests in a `bad_requests` folder. source
Requirements
Running the tool requires Java 8 or higher and Gradle. source
Results
The tool reports request details and whether responses matched expectations, writes TestNG results under build/testng-results, and stores bad requests in a bad_requests folder. source
Specification support
The required specification is Swagger 2.0 in JSON or YAML format. source
Support
The README directs users to source code documentation and gives an email address for questions; it directs bug reports to GitHub Issues. source
Test scenarios
Supported scenarios include requests with generated valid values and requests that inject a random invalid value into each checked parameter. source
Windows
The README gives `gradlew.bat build` as the Windows build command. source
Windows and Linux
The README gives build instructions for Windows and describes how to create a Linux executable. source

Checked against the maker's pages on 8 Oct 2026.