wireshark
Auth/lab ref: network and wireless protocol analyzer for capturing and inspecting packets.
v2026.11.13-21cd5682 instalações+2 em 7 dias39 EstrelasGPL-2.0sincronizado há 11 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/wiresharkGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote0508491c…4e4b2d07
0508491cc0f5…33e84e4b2d074 arquivos · 7.3 KBVarreduraBaixonenhum achado
Fontegithub.com/AeonDave/malskill/tree/main/offensive-tools/network/wireshark@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Packet capture and protocol analysis for wired and 802.11 wireless traffic.
Quick Start (tshark CLI)
tshark -i eth0 -w capture.pcap
tshark -r capture.pcap -Y "http" -T fields -e http.host -e http.request.uri
tshark -r capture.pcap -Y "ntlmssp" -T fields -e ip.src -e ntlmssp.auth.username
# Wireless examples
tshark -r wifi.pcap -Y "wlan.fc.type_subtype == 0x08" -T fields -e wlan.bssid -e wlan.ssid
tshark -r wifi.pcap -Y "eapol"
tshark -r wifi.pcap -Y "tls.handshake.certificate"Key Display Filters
| Filter | Purpose |
|---|---|
tcp.port == 445 |
SMB traffic |
http.request.method == "POST" |
POST requests |
ftp.request.command == "PASS" |
FTP passwords |
ntlmssp |
NTLM auth |
kerberos |
Kerberos traffic |
dns |
DNS queries |
ip.addr == 10.0.0.5 |
Traffic to/from IP |
eapol |
WPA/WPA2 4-way handshake traffic |
wlan.fc.type == 0 |
802.11 management frames |
wlan.fc.type_subtype == 0x08 |
Beacon frames |
wlan.fc.type_subtype == 12 |
Deauthentication frames |
wlan.bssid == 00:11:22:33:44:55 |
Traffic for one AP |
tls.handshake.certificate |
Certificates inside WPA-Enterprise / TLS handshakes |
Common Workflows
Triage a .pcap before deep inspection
# What protocols dominate the capture?
tshark -r capture.pcap -q -z io,phs
# Which hosts talk the most?
tshark -r capture.pcap -q -z endpoints,ip
# Which client/server pairs matter?
tshark -r capture.pcap -q -z conv,tcp
# Fast protocol shortlist for common IR and forensic pivots
tshark -r capture.pcap -Y "http or dns or smb or ftp or smtp or kerberos or ntlmssp"Start with protocol hierarchy, endpoints, and conversations before diving into single packets. This reduces noise and helps you pick the stream, host, or protocol worth following.
Follow TCP stream
# tshark
tshark -r capture.pcap -q -z follow,tcp,ascii,0
tshark -r capture.pcap -q -z follow,http,ascii,0
tshark -r capture.pcap -q -z follow,tcp,raw,0
# Wireshark GUI: right-click packet → Follow → TCP StreamUse Follow Stream to reconstruct the application view of a connection. In the GUI you can save the stream as ASCII for quick reading or Raw when you want to decode or carve the payload offline.
Find tokens and suspicious strings
# Broad content hunt
tshark -r capture.pcap -Y 'frame contains "token" || http contains "Authorization" || dns contains "corp"'
# Look for cookies / bearer-style tokens / auth headers
tshark -r capture.pcap -Y "http.authorization || http.cookie"
# Search for form submissions
tshark -r capture.pcap -Y 'http.request.method == "POST"'In the GUI use Edit -> Find Packet with a display filter, string, hex value, or regex when you need to jump quickly to a secret, hostname, URI, or magic byte sequence inside a large capture.
Extract credentials from capture
# HTTP POST bodies (logins)
tshark -r capture.pcap -Y "http.request.method == POST" \
-T fields -e ip.src -e http.host -e http.request.uri -e http.file_data
# FTP passwords
tshark -r capture.pcap -Y "ftp.request.command == PASS" \
-T fields -e ip.src -e ftp.request.arg
# NTLM hashes
tshark -r capture.pcap -Y "ntlmssp.auth.username" \
-T fields -e ip.src -e ntlmssp.auth.domain -e ntlmssp.auth.username
# Kerberos usernames
tshark -r capture.pcap -Y "kerberos.CNameString" \
-T fields -e ip.src -e kerberos.CNameString
# DNS queries
tshark -r capture.pcap -Y "dns.flags.response == 0" \
-T fields -e frame.time -e ip.src -e dns.qry.nameExport files from pcap
# HTTP objects (GUI)
# File → Export Objects → HTTP
# via tshark
tshark -r capture.pcap --export-objects http,./exported_files/If the interesting data is not a clean HTTP object, select the bytes or follow the stream and save the result instead. Wireshark can also export selected packet bytes and packet dissections when you need a raw blob, structured text, CSV, or JSON evidence.
Live capture + immediate output
# Capture on interface, write pcap, print to stdout
tshark -i eth0 -w capture.pcap -P
# Filter during capture
tshark -i eth0 -f "tcp port 445 or tcp port 80"
# Capture for N seconds
tshark -i eth0 -a duration:60 -w capture.pcapInspect 802.11 management and authentication traffic
# beacons
tshark -r wifi.pcap -Y "wlan.fc.type_subtype == 0x08"
# authentication + deauthentication
tshark -r wifi.pcap -Y "wlan.fc.type_subtype == 11 || wlan.fc.type_subtype == 12"
# EAPOL handshake traffic
tshark -r wifi.pcap -Y "eapol"
# WPA-Enterprise certificates
tshark -r wifi.pcap -Y "tls.handshake.certificate" -T fields -e tls.handshake.certificateReview decrypted 802.11 captures
If you already recovered the WEP or WPA key, load it in the GUI under:
Preferences -> Protocols -> IEEE 802.11 -> Decryption Keys
Or decrypt first with companion tooling and re-open the resulting capture in Wireshark / tshark.
Forensic .pcap workflow for labs and incident triage
- Open the capture and note the dominant protocols, top talkers, and suspicious endpoints.
- Filter to likely data-bearing traffic such as
http,dns,smtp,ftp,smb2, or a targetip.addr. - Use
Statistics -> ConversationsorStatistics -> Endpointsto isolate the most relevant flows. - Use
Follow -> TCP/HTTP/TLS Streamon candidate sessions to reconstruct requests, responses, commands, or embedded payloads. - Use
Edit -> Find Packetto search for tokens, usernames, filenames, cookies, URIs, or magic strings. - Export HTTP objects, selected packet bytes, or stream output, then decode offline if the payload is base64, compressed, XORed, or otherwise transformed.
- Keep notes on packet numbers, IPs, hostnames, and extracted artifacts so the evidence chain stays reproducible.
Resources
| File | When to load |
|---|---|
references/filters.md |
Complete display filter cheatsheet, credential extraction one-liners, stream analysis |
references/pcap-forensics-workflows.md |
Step-by-step .pcap triage, Follow Stream usage, object extraction, string hunting, and incident/lab workflows |
references/wireless-80211-workflows.md |
Wireless display filters, EAPOL / WPA-Enterprise review, frame-type mapping, and tshark workflows for 802.11 captures |
Arquivos desta versão
references/314.2 KB
- filters.md3.5 KB
- pcap-forensics-workflows.md7.2 KB
- wireless-80211-workflows.md3.5 KB
- SKILL.md6.5 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
A varredura não encontrou nada para apontar nesta versão.
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 0508491c | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Rede, wireless e telecom
Ver a categoria- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login