GVA/README.md

GPT_Vuln-analyzer

This is a Proof Of Concept application that demostrates how AI can be used to generate accurate results for vulnerability analysis and also allows further utilization of the already super useful ChatGPT made using openai-api, python-nmap, dnsresolver python modules and also use customtkinter and tkinter for the GUI version of the code. This project also has a CLI and a GUI interface, It is capable of doing network vulnerability analysis, DNS enumeration and also subdomain enumeration.

Requirements

• Python 3.10 or above
• All the packages mentioned in the requirements.txt file
• OpenAI API
• Bard API (MakerSuite Palm)
• HuggingFace token (with llama2 access )
• IPGeolocation API
• Wireshark and tshark (both added to path)

Usage Package

Import packages

cd package && pip3/pip install .

Simple import any of the 3 packages and then add define the variables accordingly

from GVA.scanner import NetworkScanner
from GVA.dns_recon import DNSRecon
from GVA.geo import geo_ip_recon
from GVA.jwt import JWTAnalyzer
from GVA.menus import Menus
from GVA.packet_analysis import PacketAnalysis
from GVA.ai_models import NMAP_AI_MODEL
from GVA.ai_models import DNS_AI_MODEL
from GVA.ai_models import JWT_AI_MODEL
from GVA.assets import Assets
from GVA.subdomain import sub_enum
from GVA import gui

# The components defined
dns_enum = DNSRecon()
geo_ip = geo_ip_recon()
p_ai_models = NMAP_AI_MODEL()
dns_ai_models = DNS_AI_MODEL()
port_scanner = NetworkScanner()
jwt_analizer = JWTAnalyzer()
sub_recon = sub_enum()
asset_codes = Assets()
packet_analysis = PacketAnalysis()

# KEEP IT BLANK IF YOU HAVE NO CLUE THE MENU WILL ASK TO FILL IT ONCE ACTIVE
lkey = "LLAMA API KEY"
lendpoint = "LLAMA ENDPOINT"
keyset = "AI API KEY"
output_loc = "OUTPUT LOCATION FOR PCAP"
threads = 200 # Default INT 200 but can be increased.
target_ip_hostname_or_token = "TARGET IP, HOSTNAME OR TOKEN"
profile_num = "PROFILE FOR NMAP SCAN"
ai_set = "AI OF CHOICE"
akey_set = "OPENAI API KEY"
bkey_set = "BARD API KEY"
ai_set_args = ""  # Keep it blank at any cost
llamakey = "LLAMA RUNPOD API KEY"
llamaendpoint = "LLAMA RUNPOD ENDPOINT"

Menus(
    lamma_key=lkey,
    llama_api_endpoint=lendpoint,
    initial_keyset=keyset,
    threads=threads,
    output_loc=output_loc,
    target=target_ip_hostname,
    profile_num=profile_num,
    ai_set=ai_set,
    openai_akey_set=akey_set,
    bard_key_set=bkey_set,
    ai_set_args=ai_set_args,
    llama_runpod_key=llamakey,
    llama_endpoint=llamaendpoint
)


gui.application()

Usage CLI

• First Change the "OPENAI_API_KEY", "GEOIP_API_KEY" and "BARD_API_KEY" part of the code with OpenAI api key and the IPGeolocation API key in the .env file
• For the llama-api option or specific the llama runpod serverless endpoint deployment option requires you to enter the serverless endpoint ID from runpod and also your RUNPOD API KEY

GEOIP_API_KEY = ''
OPENAI_API_KEY = ''
BARD_API_KEY = ''
RUNPOD_ENDPOINT_ID = ''
RUNPOD_API_KEY = ''

• second install the packages

pip3 install -r requirements.txt
or
pip install -r requirements.txt

• run the code python3 gpt_vuln.py

# Regular Help Menu
python gpt_vuln.py --help

# Rich Help Menu
python gpt_vuln.py --r help

# Specify target with the attack
python gpt_vuln.py --target <IP/hostname/token> --attack dns/nmap/jwt

# Specify target and profile for nmap
python gpt_vuln.py --target <IP/hostname/token> --attack nmap --profile <1-13>
(Default:1)

# Specify target for DNS no profile needed
python gpt_vuln.py --target <IP/hostname/token> --attack dns

# Specify target for Subdomain Enumeration no profile used default list file
python gpt_vuln.py --target <HOSTNAME> --attack sub

# Specify target for Subdomain Enumeration no profile used custom list file
python gpt_vuln.py --target <HOSTNAME> --attack sub --list <PATH to FILE>

# Specify target for geolocation lookup
python gpt_vuln.py --target <IP> --attack geo

# Specify PCAP file for packet analysis
python gpt_vuln.py --target <PCAP FILE> --attack pcap --output <OUTPUT FILE LOCATION> --thread NUM of threads <200:default>

# Specify the AI to be used for nmap
python gpt_vuln.py --target <IP> --attack nmap --profile <1-5> --ai llama /llama-api /bard / openai <default>

# Specify the AI to be used for dns
python gpt_vuln.py --target <IP> --attack dns --ai llama /llama-api /bard / openai <default>

# Specify the AI to be used for JWT analysis
python gpt_vuln.py --target <token> --attack jwt --ai llama /llama-api /bard / openai <default>

# Interactive step by step cli interface
python gpt_vuln.py --menu True

CLI Interface Option

  ________________________
| GVA Usage in progress... |
  ========================
                        \
                         \
                           ^__^
                           (oo)\_______
                           (__)\       )\/\
                               ||----w |
                               ||     ||
┏━━━━━━━━━┳━━━━━━━━━━━━━━━━┓
┃ Options ┃ Utility        ┃
┡━━━━━━━━━╇━━━━━━━━━━━━━━━━┩
│ 1       │ Nmap Enum      │
│ 2       │ DNS Enum       │
│ 3       │ Subdomain Enum │
│ 4       │ GEO-IP Enum    │
| 5       | JWT Analysis   |
| 6       | PCAP Analysis  |
│ q       │ Quit           │
└─────────┴────────────────┘
Enter your choice:

The CLI interface has a few things to note.

• The API keys must be provided manually.
• The ones defined in the .env files work with the args options
• The process is similar but more organized.

My views on Bard

Its same as Openai GPT3.5 but faster. It can generate the same answer but in 2 times the speed.

OS Supported

Preview	Code	Name	Working Status	OpenAI Status	Bard Status	LLama2 Status
	LIN	GNU/Linux	✅	✅	✅	❌ [did not test]
	WIN	Windows	✅	✅	✅	✅

Understanding the code

Profiles:

Parameter	Return data	Description	Nmap Command
p1	json	Effective Scan	-Pn -sV -T4 -O -F
p2	json	Simple Scan	-Pn -T4 -A -v
p3	json	Low Power Scan	-Pn -sS -sU -T4 -A -v
p4	json	Partial Intense Scan	-Pn -p- -T4 -A -v
p5	json	Complete Intense Scan	-Pn -sS -sU -T4 -A -PE -PP -PY -g 53 --script=vuln
p6	json	Comprehensive Service Version Detection	-Pn -sV -p- -A
p7	json	Aggressive Scan with OS Detection	-Pn -sS -sV -O -T4 -A
p8	json	Script Scan for Common Vulnerabilities	-Pn -sC
p9	json	Intense Scan, All TCP Ports	-Pn -p 1-65535 -T4 -A -v
p10	json	UDP Scan	-Pn -sU -T4
p11	json	Service and Version Detection for Top Ports	-Pn -sV --top-ports 100
p12	json	Aggressive Scan with NSE Scripts for Vulnerabilities	-Pn -sS -sV -T4 --script=default,discovery,vuln
p13	json	Fast Scan for Common Ports	-Pn -F

The profile is the type of scan that will be executed by the nmap subprocess. The Ip or target will be provided via argparse. At first, the custom nmap scan is run which has all the crucial arguments for the scan to continue. Next, the scan data is extracted from the huge pile of data driven by nmap. the "scan" object has a list of sub-data under "tcp" each labelled according to the ports opened. once the data is extracted the data is sent to the openai API Davinci model via a prompt. the prompt specifically asks for a JSON output and the data also to be used in a certain manner.

The entire structure of request that has to be sent to the openai API is designed in the completion section of the Program.

class NetworkScanner():
    def scanner(self, AIModels, ip: Optional[str], profile: int, akey: Optional[str], bkey: Optional[str], lkey, lendpoint, AI: str) -> str:
        profile_arguments = {
            1: '-Pn -sV -T4 -O -F',
            2: '-Pn -T4 -A -v',
            3: '-Pn -sS -sU -T4 -A -v',
            4: '-Pn -p- -T4 -A -v',
            5: '-Pn -sS -sU -T4 -A -PE -PP  -PY -g 53 --script=vuln',
            6: '-Pn -sV -p- -A',
            7: '-Pn -sS -sV -O -T4 -A',
            8: '-Pn -sC',
            9: '-Pn -p 1-65535 -T4 -A -v',
            10: '-Pn -sU -T4',
            11: '-Pn -sV --top-ports 100',
            12: '-Pn -sS -sV -T4 --script=default,discovery,vuln',
            13: '-Pn -F'
        }
        # The scanner with GPT Implemented
        nm.scan('{}'.format(ip), arguments='{}'.format(profile_arguments.get(profile)))
        json_data = nm.analyse_nmap_xml_scan()
        analyze = json_data["scan"]
        match AI:
            case 'openai':
                try:
                    if akey is not None:
                        pass
                    else:
                        raise ValueError("KeyNotFound: Key Not Provided")
                    response = AIModels.GPT_AI(akey, analyze)
                except KeyboardInterrupt:
                    print("Bye")
                    quit()
            case 'bard':
                try:
                    if bkey is not None:
                        pass
                    else:
                        raise ValueError("KeyNotFound: Key Not Provided")
                    response = AIModels.BardAI(bkey, analyze)
                except KeyboardInterrupt:
                    print("Bye")
                    quit()
            case 'llama':
                try:
                    response = AIModels.Llama_AI(analyze, "local", lkey, lendpoint)
                except KeyboardInterrupt:
                    print("Bye")
                    quit()
            case 'llama-api':
                try:
                    response = AIModels.Llama_AI(analyze, "runpod", lkey, lendpoint)
                except KeyboardInterrupt:
                    print("Bye")
                    quit()
        self.response = response
        text = str(self.response)
        return text

Regex

We use Regex to extract only the important information from the custom prompt provided this reduces the total amount of unwanted data

def extract_data(json_string):
    # Define the regular expression patterns for individual values
    critical_score_pattern = r'"critical score": \["(.*?)"\]'
    os_information_pattern = r'"os information": \["(.*?)"\]'
    open_ports_pattern = r'"open ports": \["(.*?)"\]'
    open_services_pattern = r'"open services": \["(.*?)"\]'
    vulnerable_service_pattern = r'"vulnerable service": \["(.*?)"\]'
    found_cve_pattern = r'"found cve": \["(.*?)"\]'

    # Initialize variables for extracted data
    critical_score = None
    os_information = None
    open_ports = None
    open_services = None
    vulnerable_service = None
    found_cve = None

    # Extract individual values using patterns
    match = re.search(critical_score_pattern, json_string)
    if match:
        critical_score = match.group(1)

    match = re.search(os_information_pattern, json_string)
    if match:
        os_information = match.group(1)

    match = re.search(open_ports_pattern, json_string)
    if match:
        open_ports = match.group(1)

    match = re.search(open_services_pattern, json_string)
    if match:
        open_services = match.group(1)

    match = re.search(vulnerable_service_pattern, json_string)
    if match:
        vulnerable_service = match.group(1)

    match = re.search(found_cve_pattern, json_string)
    if match:
        found_cve = match.group(1)

    # Create a dictionary to store the extracted data
    data = {
        "critical score": critical_score,
        "os information": os_information,
        "open ports": open_ports,
        "open services": open_services,
        "vulnerable service": vulnerable_service,
        "found cve": found_cve
    }

    # Convert the dictionary to JSON format
    json_output = json.dumps(data)

    return json_output


def AI(key: str, data: Any) -> str:
    openai.api_key = key
    try:
        prompt = f"""
        Do a NMAP scan analysis on the provided NMAP scan information
        The NMAP output must return in a JSON format accorging to the provided
        output format. The data must be accurate in regards towards a pentest report.
        The data must follow the following rules:
        1) The NMAP scans must be done from a pentester point of view
        2) The final output must be minimal according to the format given.
        3) The final output must be kept to a minimal.
        4) If a value not found in the scan just mention an empty string.
        5) Analyze everything even the smallest of data.

        The output format:
        {{
            "critical score": [""],
            "os information": [""],
            "open ports": [""],
            "open services": [""],
            "vulnerable service": [""],
            "found cve": [""]
        }}

        NMAP Data to be analyzed: {data}
        """
        # A structure for the request
        completion = openai.Completion.create(
            engine=model_engine,
            prompt=prompt,
            max_tokens=1024,
            n=1,
            stop=None,
        )
        response = completion.choices[0].text
        return extract_data(str(response))
    except KeyboardInterrupt:
        print("Bye")
        quit()

The AI code defines an output format and commands the AI to follow a few pre-determined rules to increase accuracy. The regex extraction code does the extraction and further the main function arranges them into tables.

Using Bard AI

For you to use Bard AI you must signup to the MakerSuit Palm API for developer access and generate your API key from there. For links and how this works you can use this video MakerSuit

Once the API is acquired just add it to the .env file and you are good to go.

Using LLama2 AI

Using LLama2 is one of the best offline and free options out there. It is currently under improvement I am working on a prompt that will better incorporate cybersecurity perspective into the AI. I have to thank @thisserand and his llama2_local repo and also his YT video YT_Video. They were great resources. To be frank the llama2 code is 95% his, I just yanked the code and added a Flask API functionality to it.

The Accuracy of the AI offline and outside the codes test was great and had equal accuracy to openai or bard but while in code it was facing a few issues may be because of the prompting and all. I will try and fix it. The speed depends on your system and the GPU and CPU configs you have. currently, it is using the TheBloke/Llama-2-7B-Chat-GGML model and can be changed via the portscanner and dnsrecon files.

For now, the llama code and scans are handled differently. After a few tests, I found out llama needs to be trained a little to operate like how I intended it to work so it needs some time. Any suggestions on how I can do that can be added to the discussions of this repo Discussions Link. For now, the output won't be a divided list of all the data instead will be an explanation of the vulnerability or issues discovered by the AI.

Output

JWT Output:

                                            GVA Report for JWT
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Variables           ┃ Results                                                                          ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ Algorithm Used      │ HS256                                                                            │
│ Header              │ eyJhbGciOiAiSFMyNTYiLCAidHlwIjogIkpXVCJ9                                         │
│ Payload             │ eyJzdWIiOiAiMTIzNDU2Nzg5MCIsICJuYW1lIjogIkpvaG4gRG9lIiwgImlhdCI6IDE1MTYyMzkwMjJ9 │
│ Signature           │                                                                                  │
│ PossibleAttacks     │ None identified                                                                  │
│ VulnerableEndpoints │ Unable to determine without additional information                               │
└─────────────────────┴──────────────────────────────────────────────────────────────────────────────────┘

Nmap output:

OpenAI and Bard:

┏━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Elements           ┃ Results                                             ┃
┡━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ critical score     │ High                                                │
│ os information     │ Microsoft Windows 11 21H2                           │
│ open ports         │ 80, 22, 445, 902, 912                               │
│ open services      │ http, ssh, microsoft-ds, vmware-auth, vmware-auth   │
│ vulnerable service │ OpenSSH                                             │
│ found cve          │ CVE-2023-28531                                      │
└────────────────────┴─────────────────────────────────────────────────────┘

LLama2

╭───────────────────────────────────────────── The GVA LLama2 ──────────────────────────────────────────────╮
│                                                                                                           │
│                                                                                                           │
│                                                                                                           │
│  Based on the provided NMAP data, I have conducted a thorough analysis of the target system's open ports  │
│  and services, vulnerabilities, and operating system information. Here is my findings: Critical Score:    │
│  The critical score for this target system is 7 out of 10. The system has several open ports that could   │
│  potentially be exploited, including port 80 (HTTP), port 135 (RPC), and port 445 (Microsoft DS). While   │
│  These ports are not necessarily vulnerable, they do indicate that the system is running services that    │
│  could be targeted by attackers. Additionally, the system has an outdated version of Microsoft IIS        │
│  running on port 80, which could be a potential vulnerability. OS Information: The target system is       │
│  running Microsoft Windows 10 1607. Open Ports and Services: The target system has the following open     │
│  ports:                                                                                                   │
│                                                                                                           │
│   • Port 80: HTTP (Microsoft IIS httpd)                                                                   │
│   • Port 135: RPC (Microsoft Windows RPC)                                                                 │
│   • Port 445: Microsoft DS                                                                                │
│   • Port 8000: Splunkd httpd All of these ports are currently open and have a state of "open".            │
│     Vulnerable Services: Based on the CVEs found in the NMAP data, there are several potential            │
│     vulnerabilities in the target system's services. These include:                                       │
│   • CVE-2019-1489: An elevation of privilege vulnerability in Microsoft IIS that could be exploited by    │
│     an attacker to gain control of the system. This vulnerability is related to the outdated version of   │
│     Microsoft IIS running on port 80.                                                                     │
│   • CVE-2017-0143: A remote code execution vulnerability in Microsoft Windows RPC that could be           │
│     exploited by an attacker to execute arbitrary code on the target system. This vulnerability is        │
│     related to the outdated version of Microsoft Windows RPC running on port 135.                         │
│   • CVE-2020-1362: A remote code execution vulnerability in Microsoft DS that could be exploited by an    │
│     attacker to execute arbitrary code on the target system. This vulnerability is related to the         │
│     outdated version of Microsoft DS running on port 445. Found CVEs: The following C                     │
│                                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────╯

DNS Output:

target is jainuniversity.ac.in

┏━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Elements ┃ Results                                                                                                           ┃
┡━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ A        │ 172.67.147.95", "104.21.41.132                                                                                    │
│ AAA      │                                                                                                                   │
│ NS       │ mia.ns.cloudflare.com.","paul.ns.cloudflare.com.                                                                  │
│ MX       │ 30 aspmx5.googlemail.com.","30 aspmx4.googlemail.com.","20 alt2.aspmx.l.google.com.","30                          │
│          │ aspmx3.googlemail.com.","30 aspmx2.googlemail.com.","20 alt1.aspmx.l.google.com.","10 aspmx.l.google.com.         │
│ PTR      │                                                                                                                   │
│ SOA      │ mia.ns.cloudflare.com. dns.cloudflare.com. 2309618668 10000 2400 604800 3600                                      │
│ TXT      │ atlassian-sending-domain-verification=5b358ce4-5ad3-404d-b4b4-005bf933603b","include:_spf.atlassian.net           │
└──────────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

GEO Location output:

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Identifiers                 ┃ Data                                                                    ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ ip                          │ █████████████                                                           │
│ continent_code              │ AS                                                                      │
│ continent_name              │ Asia                                                                    │
│ country_code2               │ IN                                                                      │
│ country_code3               │ IND                                                                     │
│ country_name                │ India                                                                   │
│ country_capital             │ New Delhi                                                               │
│ state_prov                  │ Haryana                                                                 │
│ state_code                  │ IN-HR                                                                   │
│ district                    │                                                                         │
│ city                        │ Gurugram                                                                │
│ zipcode                     │ 122003                                                                  │
│ latitude                    │ 28.44324                                                                │
│ longitude                   │ 77.05501                                                                │
│ is_eu                       │ False                                                                   │
│ calling_code                │ +91                                                                     │
│ country_tld                 │ .in                                                                     │
│ languages                   │ en-IN,hi,bn,te,mr,ta,ur,gu,kn,ml,or,pa,as,bh,sat,ks,ne,sd,kok,doi,mni,… │
│ country_flag                │ https://ipgeolocation.io/static/flags/in_64.png                         │
│ geoname_id                  │ 9148991                                                                 │
│ isp                         │ Bharti Airtel Limited                                                   │
│ connection_type             │                                                                         │
│ organization                │ Bharti Airtel Limited                                                   │
│ currency.code               │ INR                                                                     │
│ currency.name               │ Indian Rupee                                                            │
│ currency.symbol             │ ₹                                                                       │
│ time_zone.name              │ Asia/Kolkata                                                            │
│ time_zone.offset            │ 5.5                                                                     │
│ time_zone.current_time      │ 2023-07-11 17:08:35.057+0530                                            │
│ time_zone.current_time_unix │ 1689075515.057                                                          │
│ time_zone.is_dst            │ False                                                                   │
│ time_zone.dst_savings       │ 0                                                                       │
└─────────────────────────────┴─────────────────────────────────────────────────────────────────────────┘

PCAP OUTPUT

Collecting Json Data
Extracting IP details...
Extracting DNS details...
Extracting EAPOL details...
Extracting TCP STREAMS details...
TCP streams can take some time..
Total Streams combination:  252
Number of workers in progress:  250
Completed
                                                            GVA Report for PCAP
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Identifiers                        ┃ Data                                                                                               ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ PacketAnalysis.Services            │ ['49943', '49958', '49934', '49944', '49931', '443', '49957']                                      │
│ PacketAnalysis.TCP Streams         │ ['1', '4', '5', '2', '0', '3']                                                                     │
│ PacketAnalysis.Sources Address     │ ['█████████████', '1.1.1.1', '█████████████', '█████████████', '█████████████', '█████████████']   │
│ PacketAnalysis.Destination Address │ ['█████████████', '1.1.1.1', '█████████████', '█████████████', '█████████████', '█████████████']   │
│ PacketAnalysis.DNS Resolved        │ []                                                                                                 │
│ PacketAnalysis.DNS Query           │ ['oneclient.sfx.ms']                                                                               │
│ PacketAnalysis.DNS Response        │ ['oneclient.sfx.ms.edgekey.net', 'e9659.dspg.akamaiedge.net', 'oneclient.sfx.ms']                  │
│ PacketAnalysis.EAPOL Data          │ []                                                                                                 │
│ PacketAnalysis. Total Streams Data │ 126                                                                                                │
└────────────────────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘

Usage GUI

The GUI uses customtkinter for the running of the code. The interface is straight forward the only thing required to remember is:

• When using dns attack dont specify the profile

python GVA_gui.py

main window

output_DNS

output_nmap

oytput_geo

Advantage

• Can be used in developing a more advanced systems completly made of the API and scanner combination
• Has the capability to analize DNS information and reslove Mustiple records it a more better format.
• Can increase the effectiveness of the final system
• Can also perform subdomain enumeration
• Highly productive when working with models such as GPT3