netflows
/netflows
Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures.
- Author
- BrownFineSecurity ↗
- Repository
- iothackbot ↗
- Licence
- MIT
- Last repository change
- 01.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures.
Original author description
Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures.
How it works
- Tool Overview
- Instructions
- Usage
- Parameters
- Examples
- Output Information
- Use Cases
- Important Notes
SKILL.md preview
--- name: netflows description: Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures. --- # NetFlows - Network Flow Extractor with DNS Resolution You are helping the user extract and analyze network flows from packet capture files using the netflows tool. ## Tool Overview NetFlows analyzes pcap/pcapng files to: - Extract unique TCP and UDP flows (destination IP:port pairs) - Build a DNS resolution table from DNS responses in the capture - Automatically resolve IP addresses to hostnames where possible - Filter flows by source IP address - Generate a summary of all network destinations contacted This is particularly useful for IoT device analysis to understand what external services a device communicates with. ## Instructions When the user asks to analyze network flows, extract destinations, or identify what hosts a device talks to: 1. **Gather requirements**: - Get the pcap/pcapng file path(s) - Ask if they want to filter by a specific source IP (e.g., the IoT device's IP) - Determine preferred output format 2. **Execute the analysis**: - Use the netflows command from the iothackbot bin directory 3. **Interpret results**: - Explain resolved hostnames and their significance - Note any unresolved IPs that may need further investigation - Highlight interesting patterns (cloud services, P2P connections, etc.) ## Usage ### Basic Analysis Analyze a pcap file showing all flows: ```bash netflows capture.pcap ``` ### Filter by Source IP Extract flows from a specific device: ```bash netflows capture.pcap --source-ip 192.168.1.100 ``` ### Multiple Files Analyze multiple capture files: ```bash netflows capture1.pcap capture2.pcapng ``` ### Output Formats ```bash # Human-readable colored output (default) netflows capture.pcap --format text # Machine-readable JSON netflows capture.pcap --format json # Minimal output - just hostname:port list netflows capture.pcap --format quiet ``` ## Parameters **Input:** - `pcap_files`: One or more pcap/pcapng files to analyze (required) **Filtering:** - `-s, --source-ip`: Filter flows originating from this IP address **Output:** - `--format text|json|quiet`: Output format (default: text) - `-v, --verbose`: Enable verbose output ## Examples Analyze IoT device traffic: ```bash netflows iot-capture.pcap --source-ip 192.168.1.50 ``` Get just the flow list for scripting: ```bash netflows capture.pcap -s 10.0.0.100 --format quiet ``` JSON output for parsing: ```bash netflows capture.pcap --format json | jq '.data[].flow_summary' ``` ## Output Information **Text format includes:** - DNS mappings discovered (IP -> hostname) - TCP flows with hostname resolution status - UDP flows with hostname resolution status - Consolidated flow summary (hostname:port or ip:port) **JSON format includes:** - `dns_mappings`: Dictionary of IP to hostname mappings - `tcp_flows`: List of TCP flow objects with hostname, ip, port - `udp_flows`: List of UDP flow objects with hostname, ip, port - `flow_summary`: List of "hostname:port" or "ip:port" strings - `dns_queries`: List of DNS domains queried - `total_packets`: Number of packets analyzed ## Use Cases 1. **IoT Device Profiling**: Identify all cloud services and endpoints an IoT device communicates with 2. **Network Forensics**: Enumerate destinations contacted during an incident 3. **Privacy Analysis**: Discover telemetry and tracking endpoints 4. **Firewall Rule Creation**: Generate allowlist/blocklist of endpoints 5. **Malware Analysis**: Identify C2 servers and exfiltration destinations ## Important Notes - The tool resolves hostnames using DNS responses found within the same pcap file - IPs without corresponding DNS lookups in the capture will show as "unresolved" - Supports both pcap and pcapng formats - Does not require elevated privileges (unlike live capture tools) - Large pcap files may take time to process
Versions
The database has no other skills named netflows.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8062755252f5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pcap-analysis
Use when analyzing network packet capture files (.pcap, .pcapng) for DNS errors, TCP connection failures, HTTP proxy issues, or any network-level investigation using tshark on the local workstation - 100pcap-workflow
Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析. - 90packet-analysis
Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol. - 100analyze-network-capture
Analyze an authorized saved PCAP or PCAPNG with bounded TShark recipes and produce governed frame and stream evidence. Use for packet troubleshooting, protocol inspection, or optional local Termshark review. - 90iec104-forensics
Analyze offline IEC 60870-5-104 TCP/2404 PCAP or PCAPNG captures for ASDU types, information object addresses, command candidates, sequence numbers, and CTF evidence. Use for telecontrol, power grid SCADA and IEC-104 packet investigations. - 90protocol-traffic-analysis
Analyzes supplied PCAP and packet-capture evidence into hosts, conversations, dependencies, authentication exposure, timing patterns, blind spots, and defensible follow-up. Use when reviewing network traffic without transmitting to the observed systems.