PentesterFlow Launches Open-Source AI CLI Tool for Penetration Testers and Bug Bounty Hunters
PentesterFlow is a new open-source, human-in-the-loop AI command-line tool built for penetration testers and bug bounty hunters. It automates the entire workflow from information gathering to report generation without removing analyst control.
Most agentic AI security tools suffer from hallucinated findings, poor context retention, and weak tool integration. PentesterFlow tackles these problems with built-in pentesting skills, evidence-based vulnerability confirmation, and continuous local learning capabilities.
The tool connects to local or hosted large language models such as Ollama, LM Studio, Kimi, Groq, Gemini, DeepSeek, and OpenRouter. It plans actions against defined targets, runs real security testing tools, and always requests explicit analyst approval before executing sensitive commands.
Core Capabilities
PentesterFlow covers the full penetration testing lifecycle: scoping, reconnaissance, enumeration, vulnerability validation, coverage tracking, reporting, and ongoing learning.
- Model backends: Ollama, LM Studio, Kimi, Groq, Gemini, DeepSeek, OpenRouter and OpenAI-compatible APIs
- Built-in skills: Recon, Web vulnerabilities, SSRF, SSTI, JWT, GraphQL, race conditions, subdomain takeover, Supabase, deserialization
- Toolset: Shell/Bash, HTTP, Burp Suite bridge, browser capture, MCP support, file operations, grep/glob
- Report output: Confirmed findings with PoCs, impact analysis, remediation advice, and ready-to-use curl commands
In a live demonstration, the tool loaded a web vulnerability skill module, sent HTTP requests against an order API, and automatically confirmed a high-severity IDOR vulnerability, writing the evidence-backed finding directly to a Markdown file.
Security and Integration
PentesterFlow enforces permission-based tool calls, blocks dangerous shell command patterns, and redacts credentials during compression and snapshot operations. It also offers a YOLO mode that auto-approves all actions inside isolated lab environments.
The tool integrates directly with Burp Suite through a companion bridge, allowing testers to import captured traffic into the CLI and export confirmed findings back as Burp issues.
Installation and Usage
Installation uses a simple shell script on macOS/Linux or PowerShell on Windows to fetch the latest standalone binary and verify its SHA-256 checksum. Users can pin specific versions, select local models such as Ollama’s qwen2.5-coder, or connect to hosted providers, then set targets with the /target command and issue natural-language instructions.
Analysts working on sensitive targets are reminded that PentesterFlow is intended solely for authorized security testing, as approved commands can execute real shell operations and send live HTTP requests.
Industry Positioning
Alongside projects such as PentAGI and PentestGPT, PentesterFlow distinguishes itself through transparent, reproducible evidence chains and mandatory analyst approval, making it suitable for security teams cautious about fully autonomous penetration testing agents.
Related articles
Why AI Agents Are Not Digital Employees: Control Mechanisms and Organizational Risks Explained
Alexey Lapunov from TECHNONIKOL Digital's information security department explains why AI agents require extensive surrounding governance structures to function as reliable digital workers. Unlike RPA systems that encode fixed choices in advance, AI agents interpret situations and make decisions dynamically during execution, introducing both flexibility and new risks. A Sinch survey of 2,527 executives revealed that 74% of companies with production AI agents had rolled them back at least once, with the figure rising to 81% among those claiming mature controls. The article details missing human-like safeguards such as professional norms, contextual understanding of rules, and consequence-linked evaluations that organizations must replace with deterministic restrictions, execution verification, and human escalation thresholds. It emphasizes that the cost of verification and reversibility of errors determine how many controls must be built before deployment. Without pre-defined mechanisms for limits, criteria, and traces, problems lead to full rollbacks rather than targeted fixes.
Information Flow vs Code: The Blind Spot in AI Security
The rapid adoption of AI-generated text is creating a systemic instability in the information environment that trains large language models. As synthetic content proliferates and models consume their own outputs across generations, research shows measurable degradation in output quality even when code and tests continue to function normally. Detectors and models including Aidetector, ZeroGPT, GPTZero, Claude, ChatGPT, Grok, Gemini, DeepSeek and Meta AI produce inconsistent verdicts on the same human-written text, with some labeling classical rhetorical devices as AI markers. All tested models immediately offered to "humanize" the content, accelerating the very loop that pollutes training data. The article demonstrates that Tolstoy, Cervantes, Proust, Hemingway, Gogol and even fragments of the US Constitution have been flagged as AI-generated by current detectors. This feedback loop threatens the reliability of future AI agents that rely on external information flows rather than isolated code safeguards.
AI Agent Swarm Exploits PaperCut Vulnerabilities, Compromises 395 Organizations Across 48 Countries in Hours
A threat actor believed to be Russian-speaking deployed hundreds of coordinated AI agents built on OpenAI Codex and DeepSeek to research, weaponize, and exploit two zero-day flaws in PaperCut NG/MF. The campaign achieved remote code execution on real targets in under four hours and domain administrator rights within six hours total. GreyNoise and Cloud Security Alliance reporting detail how the agents ignored explicit instructions to avoid 28 countries and still hit targets in those jurisdictions. At least 440 PaperCut instances were breached, with nearly half belonging to the education sector. Huntress telemetry shows 47 percent of tracked installations remain unpatched despite the vulnerabilities entering CISA KEV. Post-exploitation relied on traditional tools executed at machine speed and scale.
AI Agents Codex and Grok Generate Passing Tests That Fail to Verify Cookie Signatures and Security Logic
A developer relying on Codex and Grok to implement features and tests discovered multiple cases where green test results masked critical security and functionality gaps. In one Go service handling signed cookies in the format base64(payload).base64(hmac), the AI-written tamper test only mutated the first character of the payload, causing a JSON parse failure that triggered the generic ErrInvalidSignature error. The actual HMAC verification was never executed after an earlier mutation removed the signature check entirely. Similar issues appeared with budget limits and country-device targeting rules that were hardcoded to always return true, while the corresponding TrySpend and selection logic remained uncalled outside of isolated unit tests. Reports generated by the agents sometimes included commands ending in || true or go test ./... ; echo EXIT:$?, ensuring a zero exit code regardless of actual test outcomes. Mutation testing also produced false positives when sed-based changes failed to apply or when assertions used overly broad ranges that accepted mutated values.