recon-sector

Runs sector-parameterized reconnaissance probes against WordPress-heavy SMB target lists.

1.2k|212|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill recon-sector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon-sector
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/recon-sector
Command: npx skills add https://github.com/uphiago/recon-skills --skill recon-sector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes references (resource) components.

What problem does it solve?

Manual reconnaissance across many small-business targets in the same industry repeats identical probes with only paths and platforms changing, wasting time and producing inconsistent coverage.

Core Features & Use Cases

  • Sector-aware probing: Loads per-industry platform and high-value path data from references/sectors.yaml covering 25 sectors such as plumbing, dentists, and automotive dealers.
  • Standard probe suite: Checks WordPress presence, REST API user enumeration, CORS credential reflection, XMLRPC exposure, debug log PII leakage, directory listing, and source leaks like .env and .git.
  • Verification discipline: Defines explicit confirmation criteria so parked domains, wildcard DNS, and non-exploitable CORS headers are not reported as findings.
  • Use Case: Given a list of dental clinic domains, run the plumbing-style probe suite with the dentists sector to surface exposed debug logs, patient-portal paths, and XMLRPC endpoints, saving per-target markdown reports.

Quick Start

Run sector reconnaissance on my authorized target list by loading the dentists sector data and probing each domain for WordPress, CORS, XMLRPC, and exposed debug logs.

Frequently Asked Questions about recon-sector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run reconnaissance against a list of small business websites?

Provide a text file with one domain per line, select a sector name, and run the probe suite which loads sector-specific paths from sectors.yaml. It checks WordPress detection, CORS reflection, XMLRPC, debug logs, and industry-specific paths per target.

What does the sector recon probe check on WordPress sites?

It checks wp-login.php presence, /wp-json/wp/v2/users for user enumeration, CORS credential reflection on the REST API, xmlrpc.php including multicall support, /wp-content/debug.log for PII, directory listing on uploads, and source leaks like .env and .git.

How do I avoid false positives from parked domains during mass recon?

Cross-check suspicious targets: if /robots.txt and /.env both return HTTP 200 with near-identical HTML bodies, mark the domain as parked and skip it. Also resolve a random subdomain first to detect wildcard DNS.

When is a CORS finding actually exploitable on a WordPress REST API?

A CORS finding is only valid when the response reflects the attacker origin in Access-Control-Allow-Origin AND sets Access-Control-Allow-Credentials: true. ACAO wildcard without credentials is not exploitable and must not be reported.

What are the limitations of sector-based reconnaissance?

It only covers the 25 predefined sectors in sectors.yaml and focuses on WordPress-dominant SMB stacks, so atypical platforms need manual probing. Rate limiting, WAFs, and parked domains also require the documented verification steps to avoid noise.