Attack workflow BETA

Send "attack:<target>" and the model confirms the possibilities the other workflows flagged — proving each with a working, non-destructive exploit — and writes a client-ready report.

These workflows are new and may have bugs.

• attack:<target>

  Reads everything the OSINT, recon and web workflows gathered about the target from the shared findings database, then turns each exploitable possibility into a confirmed vulnerability with a working, non-destructive proof of concept — and writes a client-ready report with a reproducible attack for each finding.

  findingssqlmapjwt_tooldalfoxgit-dumpernuclei

  How it works

  1. Loads the target's findings from the shared database (subdomains, ports, SQLi-possibility parameters, weak JWTs, exposed secrets and more) — it does not re-run recon.
  2. Proves each candidate non-destructively: SQL injection with sqlmap (lists databases or one row, never dumps or alters data), a forged token for a weak or none-key JWT, a dump of an exposed .git, cross-account access for IDOR, an executing marker for XSS, and a re-fired nuclei template for a known CVE.
  3. Re-runs each successful proof to confirm it reproduces.
  4. Writes a report under /root/attack/ with an executive summary and, per vulnerability: severity (CVSS) and OWASP class, the exact working proof of concept, step-by-step reproduction, the evidence, impact and remediation.

The workflow needs an active Kali Linux machine — the exploitation toolkit (sqlmap, jwt_tool, dalfox, git-dumper, nuclei) is pre-installed. Rent one in the Virtual Machines section.

Have more than one machine? Add --machine <name> (or -m <name>) — e.g. attack:example.com --machine kali-1 — to pin every command to that machine.

Every attack run saves its full report to a file on your Kali machine (under /root/attack/) and the reply gives you the exact path plus a download link.