Torque HTTP Vulnerability Scanner

by Coding, Cyberthreats, Downloads, Hacker News, Hacking, Security, Utilities

Torque Scanner

Torque Scanner is a cross‑platform network reconnaissance and audit tool designed to perform repeated HTTP requests with randomized user agent rotation, timing jitter, and optional Tor routing. It provides real‑time feedback through a web‑based control panel which automatically launches in your default browser.

Download Bundle

1. Launching the Application

Run the binary appropriate for your system:

./torque-scanner      (Linux / macOS)
torque-scanner.exe    (Windows)

On launch, Torque Scanner starts a small local web server and attempts to open your browser automatically. If it does not open, the terminal will display the URL:

http://127.0.0.1:xxxxx/

Copy this into your browser manually.

2. The Control Panel Interface

Once opened, you will see the main interface containing:

Target URL – The website or endpoint to be scanned.
Request Count – Total number of HTTP GET requests to send.
Concurrency – Number of workers (threads).
Jitter Settings – Random timing delays between requests.
Retry & Backoff Settings – Controls how failed requests are repeated.
Tor Settings:
- Use Tor – Routes traffic through a SOCKS5 Tor proxy at 127.0.0.1:9050.
- Tor NEWNYM – Requests a new Tor identity between requests (requires the Tor control port at 127.0.0.1:9051).
Real‑time Output Panel – Displays live request logs via SSE.

3. Starting a Scan

Enter your target URL (e.g., http://example.com). Set your preferred options and click:

INITIATE ATTACK PROBE

You will see each request logged in real time, including:

Worker ID
HTTP status codes
User‑Agent string selected
Tor routing notes
Retry attempts and backoff delays

4. Stopping a Scan

CEASE ATTACK PROBE

Workers will complete any in‑progress request and halt gracefully.

5. Tor Status Indicator

At the top of the UI, Torque Scanner displays:

SOCKS5 availability (port 9050)
Control port availability (port 9051)

These indicators update every 3 seconds.

6. Log Files

All scans are logged into:

./logs/tor_scanner_YYYYMMDD_HHMMSS.log

These logs can be used for security audits, debugging, and evidence collection.

Technical Overview & Internal Architecture

1. Overview

Torque Scanner is a concurrency‑driven network interrogation tool designed to evaluate:

Endpoint rate limiting
User‑agent filtering behavior
Load balancing characteristics
Tor behavior (through different identities)
Error handling and response reliability
Infrastructure resiliency under controlled request bursts

It is not a stress‑testing tool. Its purpose is security auditing and behavioral analysis, not overwhelming a service.

2. Architecture Summary

The software is built as a single Go program embedding both an HTTP server and a full web interface.

A. Web UI Server

Serves the embedded HTML GUI.
Provides:
- /start – Begins a scan.
- /stop – Halts a scan.
- /events – SSE endpoint for live logs.

B. Worker Engine

A configurable number of goroutines pull jobs from a channel.
Each job represents a single HTTP GET request.
Workers:
- Randomize a user agent
- Sleep for jitter delay
- Attempt request with retry & exponential backoff
- Broadcast results via SSE

C. User Agent Management

Loads user-agents.txt if found.
Otherwise uses a compact built‑in list.
Random selection per request.

D. Tor Integration

Torque Scanner can direct all traffic through:

socks5://127.0.0.1:9050

Workers may optionally trigger a NEWNYM request on the control port, forcing a new Tor exit node identity.

E. Real‑Time Logs (SSE)

All activity is broadcast through Server‑Sent Events:

Low latency
Auto‑reconnecting
Live streaming to all connected browsers

F. Logging Subsystem

Every request is logged to file with:

Timestamp
Target
Worker ID
Status code
User agent
Retry attempts
Tor usage notes

3. Why Torque Scanner Is Useful

Web Security Testing
Tor privacy analysis
Endpoint reliability testing
Infrastructure diagnostics
Educational & research purposes

4. Cross‑Platform Support

Linux (x86_64, ARM, ARM64)
Windows
macOS
Raspberry Pi (ARM)

5. Ethical Usage

Torque Scanner is intended for:

Your own systems
Systems you have permission to test
Security auditing and research

Do not use it on systems where you lack authorization.

K0NxT3D

Web And Software Development Coding Scripting Branding Images Media Content Management Systems

QMap Concurrent Nmap Frontend

by Coding, Cyberthreats, Downloads, Hacker News, Hacking, Scripting, Security, Utilities, Web Development

QMap Nmap Frontend

Simple, step-by-step instructions for QMap Nmap end users. What you need and how to run QMap.

Downloads

Click to download QMap Version 2.0

Download QMap (Linux/Windows)
Download README.txt

What is QMap?

QMap is a menu-driven front end to Nmap that simplifies scanning tasks.
It supports single-target scans, concurrent multi-target scans (with rate-limiting),
progress and ETA estimation, and automatic machine-readable output files (grepable / XML / all).

System Requirements (what you must install)

Nmap	QMap requires the Nmap scanner. Install and ensure it’s in your PATH. Linux (Debian/Ubuntu): sudo apt update && sudo apt install nmap -y macOS (Homebrew): brew install nmap Windows: Download from https://nmap.org/download.html and enable “Add Nmap to PATH”.
Go	Only required if you plan to build from source. Otherwise use the provided executable. Recommended Go ≥ 1.20. Verify with go version.
Sudo / Admin	Needed only for some scan types (SYN, UDP). Linux: use sudo. Windows: run as Administrator.
Zip (optional)	Only needed for building from source if you want ZIP archives. Not required to run QMap.

How to Run QMap (quick)

Linux:
  ./qmap

Windows:
  qmap.exe

If a scan needs privileges:
  sudo ./qmap   (Linux)

On Windows, run terminal as Administrator.

Main Menu — what each item does

1) Run single target
   - Scan one IP or hostname.
2) Run multiple targets from file (concurrent)
   - Provide a file with one target per line (# for comments).
3) Toggle auto-elevate (sudo / runas)
4) Change default flags / choose scan
5) Show predefined flags list
6) Adjust concurrency
7) Choose output mode (None / -oG / -oX / -oA)
8) Toggle save combined output
9) Exit

Quick Examples

Example 1 — Single IP:
  1) Start QMap
  2) Choose "Run single target"
  3) Enter IP (e.g. 192.168.1.1)
  4) Choose scan flags (e.g. "Quick scan -F")
  5) View output / save

Example 2 — Multi-target:
  targets.txt:
    192.168.1.1
    scanme.nmap.org

  1) Start QMap
  2) "Run multiple targets from file"
  3) Enter targets.txt
  4) Choose flags/concurrency/output

Output Files & Where to Find Them

QMap creates timestamped files in the same directory:

scan-192.168.1.1-20251109-182000.txt
scan-192.168.1.1-20251109-182000.xml
combined-scan-targets-20251109-182030.txt

Tips & Troubleshooting

• "nmap: command not found" — install Nmap.
• "permission denied" — run QMap with sudo / Administrator.
• Slow scans — increase concurrency.
• Windows elevation issues — run elevated PowerShell/Command Prompt.
• Never scan networks without authorization.

Important Legal Note

Only scan systems and networks that you own or are explicitly authorized to test.
Unauthorized scanning may be illegal.

Download QMAP (Version 2.0.1):

QMap For Linux & Windows

All Files Included 3.4MB

Port Scanner Using Bash Netcat Nmap

by Automation, Bash Scripting, Coding, Port Scanners, Scripting, Utilities, Web Design, Web Development

A simple and easy to use port scanner that allows the user to input a URL or IP Address and Port Range to scan using Netcat and Nmap and also works exceptionally well with proxychains.

#!/bin/bash
date="$(date +%y-%m-%d_%H:%M:%S)"
log="$date.log"
touch $log
clear
    echo "Enter URL:"
     read url
    echo "Start Port:"
     read Sport
    echo "End Port:"
     read Eport
clear
    port=0
        while [ $port -lt $Eport ]; do
        nc -z -v $url $port 2>&1 | grep succeeded && echo $port >> $log
        let port=port+1 
    done
        while IFS= read -r openport
    do
        clear
        echo "Scanning $url - CTRL C to Abort"
        nmap -p $openport $url >> $url.txt
    sleep 5
    clear
done < $log
rm $log

Tag Scanner