Individual skill

blackbox-web-audit

Authorized black-box web/API audit WITHOUT test accounts — unauth probing discipline, unauth-IDOR rounds using leaked IDs, JS-bundle-first attack surface mapping, non-destructive gates, and local report delivery conventions (no zip, follow sibling example folder). Use when asked to audit/pentest a target where you hold no credentials, and when writing the local report deliverable afterwards.

skills/security/blackbox-web-audit/SKILL.md

Read pinned source

Source commit 961a0dd3d2d2f66a07a416ade3b1d4473b64802e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,013
Repository last updated
Nov 5, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Black-Box Web Audit Without Credentials

Class workflow for authorized audits where you have NO test account (operator-requested or VDP scope). Complements the manually-authored `bb-methodology` (5-phase workflow) and `bug-bounty-reporting-workflow` (validation standard) — load those too; this skill adds the no-credentials specifics they lack.

## Hard Constraints (non-destructive discipline)

1. **GET-only on anything state-changing-adjacent.** Shutdown/reset/redeem endpoints: probe with GET even if the app uses POST; NEVER send the real state-changing verb on production (a `POST /api/version/shutdown` was deliberately never sent).
2. **Fake IDs for write-path probes.** Create-order/payment endpoints tested only with nonexistent UUIDs; expect-and-document 401.
3. **Credentials are always fake** for rate-limit/login tests. A quarantine of your own IP after 429 is *evidence the control works* — record it as such.
4. Embedded keys found in bundles get **tested live against their real API** before any claim (Firebase: `identitytoolkit.googleapis.com/v1/accounts:createAuthUri?key=` → 400 "API key not valid" = revoked, informational only).

## Attack Surface When You Have No Account

Subfinder/gau often return near-zero on these targets. The bundle IS the map:
Back to top