Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/zapWeb and bug bounty

zap

⁨Auth/lab ref: OWASP ZAP: free open-source web application scanner and intercepting proxy.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/zap

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
lNf2LlQNmk…W+imPLAw==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb281df65…d1eda0eb
b281df65665c…9046d1eda0eb2 files · ⁦3.8 KB⁩
ScanMedium5 findings
  • Link to a raw IP addressSKILL.md:155
  • Link to a raw IP addressSKILL.md:156
  • Link to a raw IP addressreferences/automation-api.md:153
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/web/zap@21cd568

Free web app scanner — active/passive DAST, API scanning, CI/CD integration.

Quick Start

bash
# Docker baseline scan (passive, safe for prod)
docker run --rm zaproxy/zap-stable zap-baseline.py -t https://target.com

# Full active scan
docker run --rm zaproxy/zap-stable zap-full-scan.py -t https://target.com

# API scan (OpenAPI spec)
docker run --rm zaproxy/zap-stable zap-api-scan.py \
    -t https://target.com/openapi.json -f openapi

# Daemon mode
zap.sh -daemon -port 8080 -host 127.0.0.1 -config api.key=MYKEY

Scan Scripts

Script Mode Use
zap-baseline.py Passive only Safe for prod — CI/CD gate
zap-full-scan.py Active (attacks) Comprehensive pentest
zap-api-scan.py Active — API focused OpenAPI / SOAP / GraphQL

zap-baseline.py Flags

Flag Purpose
-t <url> Target URL
-r <file> HTML report output
-J <file> JSON report output
-x <file> XML report output
-a Include alpha-quality passive rules
-d Debug mode
-m <min> Spider duration (default: 1)
-j Use AJAX spider
-z <options> Pass options to ZAP directly
-c <config> Config file for FAIL/WARN overrides

zap-full-scan.py Flags

Flag Purpose
-t <url> Target URL
-r <file> HTML report output
-m <min> Spider duration (minutes)
-z <options> ZAP options (e.g., -config api.key=KEY)
-a Include alpha active rules
-j Use AJAX spider
-l <level> Alert level: PASS / IGNORE / WARN / FAIL
-s <policy> Scan policy

zap-api-scan.py Flags

Flag Purpose
-t <file/url> OpenAPI/SOAP/GraphQL spec (local or URL)
-f <format> Format: openapi / soap / graphql
-r <file> HTML report
-J <file> JSON report
-n <context> Context file

Automation Framework (YAML)

Recommended approach for complex scans:

yaml
# zap-automation.yaml
env:
  contexts:
    - name: Default
      urls:
        - https://target.com
      includePaths:
        - https://target.com.*
  parameters:
    failOnError: true

jobs:
  - type: spider
    parameters:
      maxDuration: 2
      maxDepth: 5

  - type: spiderAjax
    parameters:
      maxDuration: 2

  - type: activeScan
    parameters:
      policy: Default Policy

  - type: report
    parameters:
      template: traditional-html
      reportFile: report.html

  - type: alertFilter
    rules:
      - ruleId: 10016
        newRisk: False Positive
        url: https://target.com/login
bash
zap.sh -cmd -autorun zap-automation.yaml

REST API (Daemon Mode)

bash
ZAP_KEY=your_api_key
ZAP="http://localhost:8080"

# Start scan
curl "$ZAP/JSON/spider/action/scan/?url=https://target.com&apikey=$ZAP_KEY"

# Wait for spider to complete
curl "$ZAP/JSON/spider/view/status/?scanId=0&apikey=$ZAP_KEY"

# Start active scan
curl "$ZAP/JSON/ascan/action/scan/?url=https://target.com&apikey=$ZAP_KEY"

# Check active scan progress
curl "$ZAP/JSON/ascan/view/status/?scanId=0&apikey=$ZAP_KEY"

# Get alerts
curl "$ZAP/JSON/core/view/alerts/?baseurl=https://target.com&apikey=$ZAP_KEY"

# Generate report
curl "$ZAP/OTHER/core/other/htmlreport/?apikey=$ZAP_KEY" -o report.html

Python API

python
from zapv2 import ZAPv2

zap = ZAPv2(apikey='MYKEY',
            proxies={'http': 'http://127.0.0.1:8080',
                     'https': 'http://127.0.0.1:8080'})

# Spider
zap.spider.scan('https://target.com')

# Active scan
zap.ascan.scan('https://target.com')

# Get alerts
alerts = zap.core.alerts(baseurl='https://target.com')
for alert in alerts:
    print(f"{alert['risk']}: {alert['name']} @ {alert['url']}")

Authentication Setup

bash
# Form-based: use Automation Framework
# jobs entry:
# - type: authentication
#   parameters:
#     loginPageUrl: https://target.com/login
#     loginRequestData: username={%username%}&password={%password%}
#     usernameParameter: username
#     passwordParameter: password
#   verification:
#     method: response
#     loggedInRegex: Logout
#     loggedOutRegex: Login

Common Workflows

bash
# CI/CD passive check (no attacks, no false positives)
docker run --rm \
    -v $(pwd):/zap/wrk \
    zaproxy/zap-stable zap-baseline.py \
    -t https://target.com \
    -r baseline_report.html \
    -J baseline.json

# Full scan with JSON report
docker run --rm \
    -v $(pwd):/zap/wrk \
    zaproxy/zap-stable zap-full-scan.py \
    -t https://target.com \
    -r full_scan.html

# OpenAPI scan
docker run --rm \
    -v $(pwd):/zap/wrk \
    zaproxy/zap-stable zap-api-scan.py \
    -t https://target.com/openapi.json \
    -f openapi \
    -r api_report.html

# GraphQL scan
docker run --rm \
    zaproxy/zap-stable zap-api-scan.py \
    -t https://target.com/graphql \
    -f graphql \
    -r graphql_report.html

GitHub Actions

yaml
name: ZAP Security Scan
on: [push]
jobs:
  zap_scan:
    runs-on: ubuntu-latest
    steps:
      - name: ZAP Baseline Scan
        uses: zaproxy/[email protected]
        with:
          target: 'https://target.com'
          rules_file_name: '.zap/rules.tsv'
          cmd_options: '-a'

ZAP vs Burp Suite Pro

ZAP Burp Suite Pro
Cost Free ~$400/yr
CI/CD integration Excellent Good
Manual testing Good Excellent
Active scan accuracy Medium High
API scanning Yes Yes
Extension ecosystem Community BApp Store (commercial)
Use when CI/CD, DevSecOps, API testing Manual pentest, complex apps

Resources

File When to load
references/automation-api.md Automation Framework YAML, REST API usage, Python client, CI/CD patterns

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLink · Link to a raw IP addressSKILL.md:155
  2. MediumLink · Link to a raw IP addressSKILL.md:156
  3. MediumLink · Link to a raw IP addressreferences/automation-api.md:153
  4. MediumLink · Link to a raw IP addressreferences/automation-api.md:153
  5. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568b281df65Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login