Awesome-Hacking
A collection of various awesome lists for hackers, pentesters and security researchers
- 126k
- CC0-1.0
- 4 wk ago
Self-hosted bug-bounty platform — verification-first recon & DAST, continuous monitoring. Your data stays on your machine.
Repo rootdr-backup/Reconner, read from GitHub 13 h ago. rootdr-backup has not joined Take My Repo.
rootdr-backup/Reconner is a public repo on GitHub by rootdr-backup. Self-hosted bug-bounty platform — verification-first recon & DAST, continuous monitoring. Your data stays on your machine. It declares the MIT license on GitHub. It is written mainly in Go, has 136 stars and last changed on 2026-11-16. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-20.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
Self-hosted attack-surface intelligence and verification-first DAST for authorized bug-bounty and security teams.
Quick start · Product tour · Verification model · Scanning guide · Operator guide · Documentation
Important
Reconner performs active security testing. Run it only against assets you own or have explicit permission to test. The operator is responsible for scope, request limits, program rules, stop conditions, and collected evidence.
Reconner turns a declared scope into a durable map of assets, routes, parameters, browser states, services, candidates, evidence, and verified findings. It keeps discovery separate from proof, records work that could not be attempted, and gives long-running scans real operational controls instead of treating tool stdout as the finished product.
| Capability | What it provides |
|---|---|
| Web attack surface | DNS and HTTP discovery, crawling, JavaScript/API analysis, parameters, historical URLs, content and exposure checks |
| Verification-first DAST | Context-aware XSS, SQLi, access control, server-side classes, upload validation, Nuclei intake, and class-specific proof |
| Explicit network pipeline | Opt-in IP/CIDR/range scanning with port discovery, service/banner evidence, bounded OS detection, service-aware Nuclei, and optional auth checks |
| Continuous operations | Persistent tasks, phase ledger, pause/resume/skip/cancel, resource-aware scheduling, monitoring diffs, live logs, and Telegram controls |
| Evidence and reporting | Candidate lifecycle, reproducibility evidence, screenshots, reports, and portable target research bundles |
| One self-hosted deployment | Go service, responsive React dashboard, SQLite, Chromium, Nmap, and the pinned external toolchain in one multi-architecture image |
The recommended deployment needs only Docker and Docker Compose v2.
git clone https://github.com/rootdr-backup/Reconner.git
cd Reconner
cp .env.example .env
docker compose pull reconner
docker compose up -d reconner
docker compose psOpen http://<server-ip>:8080/. If ADMIN_PASSWORD was left blank, retrieve
the generated first-run password with:
docker compose logs reconner | grep -A1 passwordVerify the deployment:
curl -fsS http://127.0.0.1:8080/api/health
For a source build, replace the pull/start commands with:
docker compose up -d --build reconner
See the operator guide for safe upgrades, backups, resource sizing, volume ownership recovery, and troubleshooting. The shorter Docker reference documents the image and Compose layout.
Create Projects manually or import public program scope from HackerOne, Bugcrowd, Intigriti, or YesWeHack. Reconner preserves the asset type instead of flattening everything into a hostname: domains, wildcards, exact pages, JavaScript files, APIs, single IPs, CIDRs, and inclusive IP ranges each enter an appropriate pipeline.
Scope changes remain operator-controlled. New upstream assets become pending events, removed or submission-ineligible assets are suspended, and exact-page or JavaScript seeds keep their path-level identity.
Web scans expose Safe, Standard, Initial Access, and custom module selection plus slow, normal, and fast request profiles. Initial Access runs only the modules that lead to panel access, remote code execution, or network pivoting — with the rest of that closure (discovery, verification) resolved automatically — for an operator who wants the fastest path to a foothold rather than full coverage. Network scans appear only for compatible assets and offer Fast, Normal, and Deep profiles. Web and network phases cannot be mixed accidentally in one task.
Whole-target scans default to prioritized, asset-first execution: every request-heavy module runs its full pipeline against the highest-priority asset (main domain, admin/API/staging-shaped hosts, high tech-signal hosts) before moving to the next, with a lighter module tier for low-score or duplicate/wildcard-catch-all tail assets. The classic module-by-module sweep remains available as an explicit opt-out.
Every phase records discovered, eligible, attempted, candidate, confirmed, rejected, blocked, and errored work. Missing credentials, tools, browser capability, identities, callbacks, or eligible inputs do not become a false “clean” result.
Findings carry detector-specific evidence while uncertain signals remain candidates. A systemic issue confirmed across many URLs of the same host (a missing header, a host-wide misconfiguration) collapses into one finding with its affected URLs listed underneath, instead of one row per URL. Admin and high-sensitive panels are content-grouped, redirect-aware, and deduplicated across hosts. Confirmed admin panels and confirmed XSS with live browser execution proof carry a captured screenshot alongside their evidence. The orange target count is reserved for actionable medium-or-higher findings instead of low-value inventory noise.
A target's own page groups its tabs by what they actually are — discovered Surface (hosts, URLs, scripts, parameters, directories, admin panels), the Vulnerabilities working area (Confirmed, Needs Review, and each dedicated detector table), and change Activity — instead of one flat, unlabeled row.
Use pause, resume, cancel, or Skip phase from the dashboard or Telegram. Browser-backed phases receive bounded cleanup and task-owned Chromium process termination, so a stuck verifier cannot hold a scheduler slot forever.
flowchart LR
A[Authorized scope] --> B[Asset discovery]
B --> C[HTTP, routes, JS, APIs and services]
C --> D[Insertion points and request identity]
D --> E[Native detectors]
D --> F[External engines]
D --> G[Browser and OAST verifiers]
E --> H[Candidate lifecycle]
F --> H
G --> H
H --> I[Confirmed findings]
H --> J[Reviewable candidates]
I --> K[Reports, alerts and monitoring]
J --> K
Independent phases can run in parallel, but expensive detector families share per-target and per-host gates. This keeps throughput across targets without silently multiplying pressure against one application.
Reconner does not promote a finding merely because a URL returned 200, a
string was reflected, a timer moved once, or a third-party tool emitted a line.
| State | Meaning |
|---|---|
| Observation | Discovery data tied to an asset, request, response, script, route, browser state, or service |
| Candidate | A signal worth review or independent verification, but not yet proven |
| Confirmed | The detector's class-specific replay or proof contract succeeded |
| Rejected | A negative control, encoding, soft-404 family, unstable timing, or replay disproved the signal |
| Blocked / unsupported | The phase could not make a valid attempt and records why |
Examples include a fresh nonce executing in Chromium for XSS, multi-signal boolean/error/timing evidence for SQLi, token-attributed callbacks for blind classes, stable denied controls plus successful replays for access-control bypasses, and independent retrieval or processing proof for dangerous uploads.
The deterministic local corpus is expected to remain clean for its named positive and negative fixtures. That is a regression contract, not a promise of zero false positives or false negatives on arbitrary applications. See the capability matrix and quality evidence.
Reconner's general XSS pipeline covers reflected and DOM XSS, with context
classification (which breakout a reflection point actually needs, and
whether a <script> block is even JS-executable in the first place) backed
by a real HTML5 parser rather than a position heuristic, and a bypass ladder
that covers unquoted-attribute breakout, non-<script>/non-<img> event-
handler vectors, and common WAF/filter evasions. Stored upload or processing
behaviors are handled by their dedicated module rather than by blindly
spraying the general XSS corpus.
Network scanning is opt-in for a single IP, CIDR, or inclusive IP range such as
192.168.1.1-192.168.1.10. ASN/CIDR org-range discovery is a separate,
explicit opt-in on top of that: it excludes shared CDN/WAF ranges (Cloudflare,
Akamai, and the rest of the same provider dataset the Deep profile's edge
exclusion uses) before ever probing them, and still requires the operator's
own WHOIS/program-scope confirmation — ASN ownership alone is never treated
as proof an address belongs in scope.
| Profile | Discovery | Optional validation |
|---|---|---|
| Fast | Curated high-signal ports | Port, banner, service, and bounded OS evidence |
| Normal | Top 1,000 TCP ports | Service-aware network Nuclei and proof-gated 401/403 checks |
| Deep | All TCP ports | Normal checks plus explicit, paced credential audits: HTTP Basic, SSH, FTP, MySQL, PostgreSQL, Redis, RDP, VNC, Telnet, SMB |
Naabu uses TCP connect discovery; ICMP is informational and never a liveness gate. Nmap fingerprints verified open ports. Recognized CDN/WAF edges and configured exclusions are removed before probing. Every credential audit shares the same authorization gate, hard attempt/time budget, and a negative-control request (a credential that can never coincidentally be valid must still be rejected before the real sweep runs — otherwise an endpoint that accepts any credential would report a false "verified weak credential" on whichever candidate happened to run first) — promoting only stable, protocol-definitive replay evidence, never a bare status-code coincidence.
Read the scanning guide before running broad scopes.
System & updates → Wordlists & payloads manages additions for subdomains, virtual hosts, directories, backups, exposures, extensions, parameters, JWT, XSS, SQLi, LFI, SSRF, SSTI, CSTI, NoSQLi, command injection, redirects, and network auth. Imports normalize category syntax, deduplicate compiled and custom entries, and report input, added, duplicate, and invalid counts. Restore removes only the custom layer and returns that category to compiled defaults.
Custom payloads extend coverage but cannot bypass a detector's proof contract.
From a target page, use Report → Download scan bundle — ZIP. The bundle contains a versioned manifest, structured discovery/finding/evidence data, phase and task state, stored screenshots, browser-state coverage, and bounded in-scope JavaScript/chunk snapshots. Redirects are scope-checked and individual fetch failures remain visible in the manifest.
Connect a BotFather bot under System → Integrations → Telegram. One bot can allowlist multiple chats with viewer, operator, or admin roles. It supports scan and finding alerts plus target and task controls, including Skip phase. Delivery uses a durable, per-chat outbox with retry and deduplication; no public webhook is required.
Commands include /status, /targets, /target, /scans, /findings,
/scan, /pause, /resume, /skip, /cancel, /addtarget, /edittarget,
and /deletetarget.
<script>/JSON block, a <textarea>, or a comment used to
auto-report as a confirmed critical finding from a substring match alone;
it now requires a real HTML5 parser to prove the breakout formed a live,
executable element;$where operator — the one NoSQLi shape
with no visible boolean/error differential at all — is now detected via
the same statistical, linear-delay-scaling timing proof SQLi's own
time-based engine already uses, reused rather than re-implemented;//api.example.com/...) was being silently
mangled into the wrong host entirely;The full technical change record is in the v4.0.0 release notes for the prior major version's changes.
The official image pins and executes every required command during its build.
| Area | Bundled tools |
|---|---|
| Discovery | subfinder, assetfinder, findomain, alterx, asnmap, scilla, naabu |
| DNS | dnsx, massdns, puredns, shuffledns |
| HTTP and crawling | httpx, katana, hakrawler, gau, waybackurls, waymore, uro |
| Content | dirsearch, feroxbuster |
| Verification | nuclei, subzy, sqlmap, nmap, Chromium |
| Runtime | Go service, SQLite, Python 3, git, tini |
The application runs as uid/gid 10001. Compose keeps NET_RAW and
NET_ADMIN only so the file-capability-scoped Nmap binary can perform bounded
OS fingerprinting. Removing those capabilities disables OS detection while
retaining TCP-connect port and service discovery.
Bootstrap values live in .env:
| Variable | Purpose | Default |
|---|---|---|
HOST_PORT |
Dashboard port on the Docker host | 8080 |
ADMIN_USER |
Initial administrator username | admin |
ADMIN_PASSWORD |
Initial password; blank generates a random value | blank |
RECON_MEMORY_LIMIT |
Whole-container memory limit | 3g |
RECON_PIDS_LIMIT |
Whole-container process limit | 512 |
Persistent settings live in /data/config.json and are managed primarily from
the dashboard. Targets, findings, users, screenshots, corpora, templates, and
configuration live in the reconner-data volume.
Never commit .env or a populated configuration file. Deployment- or
project-level identifying headers can be configured for programs that require
them; project values override global defaults and are sent only to admitted
project hosts.
| Start here | Purpose |
|---|---|
| Documentation hub | All operator, scanning, architecture, evidence, and release documents |
| Operator guide | Install, update, back up, size, recover, and troubleshoot a deployment |
| Scanning guide | Scope types, web/network plans, proof states, controls, corpora, and exports |
| Capability matrix | Module prerequisites, positive-proof contracts, and supported boundaries |
| Docker reference | Image contents, Compose layout, capabilities, and persistence |
| v4.0.0 release notes | Prior major version's release details and local regression commands |
| Contributing | Development workflow and contribution expectations |
| Security policy | Private vulnerability reporting for Reconner itself |
Direct development requires Go, Node.js/npm, a C compiler for SQLite, and the external tools needed by the modules you run locally.
make frontend
make backend
go test ./...
go vet ./...Frontend-only workflow:
cd frontend
npm ci
npm run dev
npm run buildRelease tags must match VERSION. CI verifies formatting, dependencies, unit
and race tests, deterministic detector fixtures, migrations, frontend and
browser workflows, release smoke tests, secret/source/dependency scans, and
native linux/amd64 plus linux/arm64 container builds before publication.
Normal image and source updates keep the named volume. This command does not:
docker compose down -v
The -v flag deletes the persistent volume and therefore the database,
configuration, users, targets, findings, corpora, templates, and stored
artifacts. Do not use it for a normal upgrade.
Reconner is intended for authorized security research, bug-bounty programs, and defensive assessment. Respect official scope, exclusions, rate limits, privacy requirements, and rules of engagement. Public program catalogs are a convenience cache—not legal authorization. The maintainers are not responsible for unauthorized use or resulting damage.
For a false positive, missed fixture, operational bug, or UI issue, open a GitHub issue with a minimal reproduction and sanitized logs. Private vulnerabilities in Reconner itself belong in the process described by SECURITY.md.
Community contact: @rootdr_research
If Reconner saves you time:
BBdEFMnnMFX8ZqeoXbnmYYLE49gNEygdUDy4ctuB9EiTbc1qefw45vhpwy6k0hw4gayu9qmrje9ml34l8ap7ly0x58e7c01913D6eA354DEaB1f83AD9A95B4D9EAfCaTYE2DKJZ7nNkBNEJ7uSr374ZVfKfBUYTicBuilt by RootDR for the bug-bounty community.
rootdr-backup/Reconner is a public repo on GitHub by rootdr-backup. Self-hosted bug-bounty platform — verification-first recon & DAST, continuous monitoring. Your data stays on your machine.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-16. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.

A collection of various awesome lists for hackers, pentesters and security researchers

Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Hunt down social media accounts by username across social networks

SpiderFoot automates OSINT for threat intelligence and mapping your attack surface.

A list of Free Software network services and web applications which can be hosted on your own servers

Open-source AI penetration testing tool to find and fix your app’s vulnerabilities.

TokenTwin Checker — Dual Token BAC/IDOR Tester for Burp Suite
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/rootdr-backup/ReconnerTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.
