// IoT network traffic analyzer for detecting IoT protocols and identifying security vulnerabilities in network communications. Use when you need to analyze network traffic, identify IoT protocols, or assess network security of IoT devices.
| name | iotnet |
| description | IoT network traffic analyzer for detecting IoT protocols and identifying security vulnerabilities in network communications. Use when you need to analyze network traffic, identify IoT protocols, or assess network security of IoT devices. |
You are helping the user analyze network traffic to detect IoT protocols and identify security vulnerabilities using the iotnet tool.
IoTNet analyzes network packet captures (PCAPs) or performs live traffic capture to:
When the user asks to analyze network traffic, capture IoT traffic, or assess network security:
Determine input type:
Gather requirements:
Execute the analysis:
Analyze one or more existing packet capture files:
iotnet capture1.pcap capture2.pcap
Capture and analyze traffic in real-time:
sudo iotnet -i eth0 -d 30
Input Options:
pcap_files: One or more PCAP files to analyze-i, --interface: Network interface for live captureFiltering Options:
--ip: Filter traffic by IP address-c, --capture-filter: BPF syntax filter for live capture--display-filter: Wireshark display filter for PCAP analysisLive Capture Options:
-d, --duration: Capture duration in seconds (default: 30)Analysis Options:
--config: Custom IoT detection rules configuration file
config/iot/detection_rules.json in the iothackbot directoryOutput Options:
--format text|json|quiet: Output format (default: text)-v, --verbose: Detailed outputAnalyze a packet capture file:
iotnet /path/to/capture.pcap
Live capture for 60 seconds on wifi interface:
sudo iotnet -i wlan0 -d 60
Analyze traffic for specific IP:
iotnet capture.pcap --ip 192.168.1.100
Live capture with BPF filter:
sudo iotnet -i eth0 -c "port 1883 or port 5683" -d 45
Multiple PCAPs with custom config:
iotnet file1.pcap file2.pcap --config custom-rules.json
Filter by display filter (Wireshark syntax):
iotnet capture.pcap --display-filter "mqtt or coap"
The tool can identify:
IoTNet identifies vulnerabilities such as:
Results include:
Analyze digital and analog captures from Saleae Logic MSO devices. Decode protocols like UART, SPI, I2C from exported binary files. Use when analyzing logic analyzer captures for CTF challenges, hardware reverse engineering, or protocol decoding.
Use picocom to interact with IoT device UART consoles for pentesting operations including device enumeration, vulnerability discovery, bootloader manipulation, and gaining root shells. Use when the user needs to interact with embedded devices, IoT hardware, or serial consoles.
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.
Android APK unpacking and resource extraction tool for reverse engineering. Use when you need to decode APK files, extract resources, examine AndroidManifest.xml, analyze smali code, or repackage modified APKs.
Static analysis of UEFI/BIOS firmware dumps using Intel's chipsec framework. Decode firmware structure, detect known malware and rootkits (LoJax, ThinkPwn, HackingTeam, MosaicRegressor), generate EFI executable inventories with hashes, extract NVRAM variables, and parse SPI flash descriptors. Use when analyzing firmware .bin/.rom/.fd/.cap files offline without requiring hardware access.
Advanced file finder with type detection and filesystem extraction for analyzing firmware and extracting embedded filesystems. Use when you need to analyze firmware files, identify file types, or extract ext2/3/4 or F2FS filesystems.