Skip to content

ReqEye is a CLI assistant for HTTP request analysis, designed to help security researchers, bug bounty hunters, and pentesters identify high‑value entry points worth manual testing. It does not scan targets, send traffic, or claim vulnerabilities. ReqEye focuses on where to look, not on making assumptions.

License

Notifications You must be signed in to change notification settings

URDev4ever/ReqEye

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 

Repository files navigation

ReqEye

🇺🇸 English | 🇪🇸 Español

image

ReqEye is a CLI assistant for HTTP request analysis, designed to help security researchers, bug bounty hunters, and pentesters identify high‑value entry points worth manual testing.

It does not scan targets, send traffic, or claim vulnerabilities. ReqEye focuses on where to look, not on making assumptions.

Philosophy

ReqEye does not find bugs. It finds places where bugs are likely to exist.

Modern web vulnerabilities — especially IDOR, auth bypasses, and logic flaws — are highly context‑dependent. Fully automated scanners fail at this.

ReqEye acts as a thinking assistant:

  • It analyzes raw HTTP requests
  • Detects security‑relevant patterns
  • Highlights attack surfaces and entry points
  • Suggests manual tests a human should try

No noise. No blind scanning. No false authority.


Key Features

  • Parse raw HTTP requests (Burp / DevTools style)
  • Classify endpoints by risk and purpose
  • Identify high‑value entry points (IDOR, auth, roles, state changes)
  • Detect security‑relevant indicators without overclaiming
  • Generate offline mutated requests for manual testing
  • Compare HTTP responses to spot behavioral changes
  • Produce clean, terminal‑friendly reports

What ReqEye Is NOT

  • ❌ Not an automated vulnerability scanner
  • ❌ Not a fuzzer that sends traffic
  • ❌ Not a replacement for Burp, manual analysis, or brain usage

ReqEye is meant to be used before or during manual testing to prioritize effort.


Installation

ReqEye is written in pure Python.

git clone https://github.com/urdev4ever/reqeye.git
cd reqeye
python reqeye.py

Optional Dependency

On Windows systems, ReqEye will optionally use colorama for proper ANSI color support.

If colorama is not installed, colors are automatically disabled.

pip install colorama

This dependency is optional.


Usage

python reqeye.py --help
image

Parse a Request

python reqeye.py parse request.txt

Parses and displays:

  • Method
  • Path
  • Headers
  • Query parameters
  • Body parameters

Analyze an Endpoint

python reqeye.py analyze request.txt

Outputs:

  • Endpoint classification

  • Risk score

    image
  • Identified entry points

    image
  • Security indicators

    image
  • Manual testing recommendations

    image

The follow results are from an authorized request (thx Mercado Libre)


Generate Mutated Requests (Offline)

python reqeye.py mutate request.txt

Creates modified versions of the request for:

  • IDOR testing
  • Auth bypass attempts
  • Role / privilege manipulation
  • State and logic testing

These requests are not sent — they are meant to be copied into Burp or similar tools.


Compare Responses

python reqeye.py diff response1.txt response2.txt

Highlights:

  • Status code changes
  • Significant length differences
  • Structural changes

Useful for detecting behavior changes after manual tampering.


Generate a Report

python reqeye.py report request.txt

Produces a concise report including:

  • Endpoint summary
  • Entry points found
  • Risk evaluation
  • Testing checklist

Risk Scoring

ReqEye assigns a heuristic risk score (0–100) based on:

  • Endpoint sensitivity
  • Presence of entry points
  • Authorization context
  • Parameter control indicators

The score is meant for prioritization, not proof.


Output Philosophy

ReqEye intentionally avoids statements like:

  • "This endpoint is vulnerable"
  • "Critical security flaw found"

Instead, it uses wording such as:

  • "High‑risk entry point"
  • "Manual verification recommended"
  • "Security‑relevant indicator"

This makes it safe and appropriate for bug bounty workflows. (No fluff, no BS)


Typical Workflow

  1. Capture a request (Burp / DevTools)
  2. Run reqeye analyze
  3. Review entry points and recommendations
  4. Use reqeye mutate for test variants
  5. Manually test using Burp or similar tools
  6. Compare responses if needed

Use Cases

  • Bug bounty hunting
  • Manual web pentesting
  • API security reviews
  • Learning web vulnerability logic

Disclaimer

ReqEye is a research assistance tool.

You are responsible for:

  • Staying within scope
  • Following program rules
  • Validating all findings manually

This tool exists to help humans focus where it matters most.

Final Note

ReqEye is built around a simple idea:

Good bugs are found by humans — not scanners.


Made with <3 by URDev

About

ReqEye is a CLI assistant for HTTP request analysis, designed to help security researchers, bug bounty hunters, and pentesters identify high‑value entry points worth manual testing. It does not scan targets, send traffic, or claim vulnerabilities. ReqEye focuses on where to look, not on making assumptions.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages