Skip to content

ARGOS v1.1.0 — CLI, Resume, Proxy/Auth, AI Exploit Analysis

Latest

Choose a tag to compare

@Hemiize Hemiize released this 04 Nov 06:11
· 19 commits to main since this release

What's New

Bug Fixes

  • datetime.utcnow() replaced with datetime.now() (Python 3.12+ deprecation)
  • urllib.parse imports moved to top-level — removed inline duplicates
  • Duplicate ci entry removed from subdomain SUBS list
  • run_banner_grab rebuilt with port-appropriate probes (Redis PING, HTTP HEAD, Kubernetes /healthz, etc.)

New Features

CLI Arguments

argos --target example.com --depth 2 --proxy http://127.0.0.1:8080 --cookie "session=abc" --auth admin:pass

Target Validation

Reachability check before scan starts — DNS resolve + TCP port probe with clear error message.

Scan Resume

Interrupted scans are saved per-tool to SQLite (tool_results table). On restart, ARGOS detects the partial session and offers to resume where it left off.

Proxy & Authentication Support

Route all requests through Burp/ZAP (--proxy), inject a session cookie (--cookie), or use HTTP Basic Auth (--auth). Settings persist in settings.json and are configurable via the Settings menu.

Custom Wordlists

Provide external wordlist files for directory enumeration and subdomain enumeration via Settings or --proxy / --subdomain-wordlist.

Progress Counter (X/N)

Scan progress bar now shows [3/13] style counter alongside the tool name.

Session Count on Banner

Startup banner displays the number of saved sessions.

Configurable Default Scan Depth

DEFAULT_SCAN_DEPTH in config.py sets the pre-selected depth for new scans.

AI-Powered Exploit Result Analysis

After running an exploit, the local LLM interprets the raw tool output and displays a clean result panel:

╭─── SQL Injection Test ───────────────────────────────────────────╮
│ ✔  ERFOLG                                                        │
│                                                                   │
│ Ergebnis  : Parameter ?id is vulnerable to UNION-based SQLi      │
│ Beweis    : "you have an error in your SQL syntax"               │
│ Severity  : CRITICAL                                             │
│ Next step : sqlmap -u "…" --dbs --batch                          │
╰───────────────────────────────────────────────────────────────────╯

No more scrolling through raw nmap/curl/nikto output — just success/fail + key evidence.