socket connect always returned me a timeout while nmap returned results. No clue about it.
Did anyone report that issue ?

Currently in your pypi package setup.py script you only allow for installation on Python versions 3.8 and higher.
So someone running versions < 3.8 cannot install your program with pip even though the program will run on lesser versions without issue.

Since your code is version 3.5+ compliant and a lot of systems still ship with versions < 3.8, you could easily allow it to be downloaded and installed with pip by changing line # 21 from:
'python_requires': '>=3.8,<4.0',
to
'python_requires': '>=3.5',

I thought it would be great to look for vulnerabilities too while using the nmap scan, just to add something like this:

print("\n\n\n\nLooking for vulns at the services we found:")
nmap_vulns = "nmap -p{ports} -sV --script vuln -oA {ip}.vulns {ip}".format(ports=",".join(discovered_ports), ip=target)
print(nmap_vulns)
os.system(nmap_vulns)
t4 = datetime.now()
total2 = t4 - t3
print("-" * 60)
print("Combined scan completed in "+str(total2))

System: Arch Linux
Nmap: Installed.
IP that it ran on: localhost
Option selected: 1

Threader3000 is a great tool.

I am amazed at just how fast threader3000 runs its initial scan. I've installed threader3000 on all kinds of Linux hosts with great results in all cases.

Now I have installed threader3000 on a Windows 10 machine, and I notice that the initial nmap scan, which I would expect to take a few seconds, takes 1 minute 41 seconds. I see no output until the scan completes.

Exactly the same symptom for Git Bash and Cygwin terminal windows.

When run from a normal cmd.exe prompt, I get the same result, except that I immediately see the comforting "Port nnn is open..." throughout the duration of the scan.

I have tested nmap.exe (V.7.70) by itself and found that scanning all 65,535 TCP ports on localhost takes 1.76 seconds using the T5 flag. Threader3000's initial nmap scan reliably takes 1 minute 41 seconds to complete on localhost.

This is certainly not a deal-breaker, but I am curious as to why this is happening, and what I might be able to troubleshoot and/or analyze.

The script has been working for me for a long time, but since downloaded it again recently it gives me many errors while trying to run it.
Is it just me or a bug in the script?

Thank you

OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ OSError: [Errno 24] Too many open files File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ File "/usr/lib/python3.10/socket.py", line 232, in __init__ OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files File "/usr/lib/python3.10/socket.py", line 232, in __init__ OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files OSError: [Errno 24] Too many open files

this error appeared :| ,

If the initial scan didn't find any open ports the suggested nmap scan will try to run with the flag -p, but without ports after and will produce an error without running.