brownfinesecurity
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.
bunx add-skill brownfinesecurity/iothackbot -s iotnetLoading…
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:
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.