Quickstart

🧩 Prerequisites

• Windows with PowerShell (5.1 or higher)
• Permission to scan and test the target network/devices
• Optional: Elevated PowerShell execution policy to run scripts

To allow script execution:

Set-ExecutionPolicy Bypass -Scope Process

🚀 Running EyeSpy

You can run the script directly from a PowerShell prompt:

.\EyeSpy.ps1 -Search 192.168.0.0/24

Or by Importing the script

. .\EyeSpy.ps1

Or via one-liner:

IEX (New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Miiden/EyeSpy/main/EyeSpy.ps1'); EyeSpy -Auto 10.10.10.0/24

❓ Available Parameters

Parameter	Argument	Description
-Search	IP or CIDR	Scan for open RTSP ports
-NoAuth	IP or CIDR	Scan and check authentication requirements
-Auto	IP or CIDR	Full auto scan across range
-AuthAttack	IP:Port	Attempt credential spray
-Path	RTSP path	Specify known RTSP stream path
-Username	string	Custom username for credential spray
-Password	string	Custom password for credential spray
-Creds	file path	File of username:password entries
-Timeout	int	Network receive timeout (ms)
-Common	switch	Use common RTSP paths only
-Help	switch	Display built-in help

📌 Example Commands

1. Scan network for open RTSP ports

EyeSpy -Search 192.168.1.0/24

2. Scan and check for authentication requirements

EyeSpy -NoAuth 192.168.1.100

3. Target a specific IP:Port for credential attack using a specific username and increased timeout

EyeSpy -AuthAttack 192.168.1.100:554 -User 'admin' -Timeout 2000

4. Run the full end to end process (Auto scan) over a CIDR range

EyeSpy -Auto 192.168.1.0/24

5. Custom credential spray against a designated path

EyeSpy -AuthAttack 10.10.10.0/28 -Creds C:\creds.txt -Path '0/1'

🧠 Tips

1. Use smaller CIDR ranges when testing live environments to reduce impact.
2. Combine -Verbose for diagnostic output when troubleshooting.
3. Provide only authorized credentials to avoid unnecessary brute-force.
4. Predetermine the valid path