/iotnet
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.
$ npx -y skills add brownfinesecurity/iothackbot --skill iotnet --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/iotnet
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
iotnet.SKILL.mdname: 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.
IoTNet - IoT Network Traffic Analyzer
You are helping the user analyze network traffic to detect IoT protocols and identify security vulnerabilities using the iotnet tool.
Tool Overview
IoTNet analyzes network packet captures (PCAPs) or performs live traffic capture to:
- Detect IoT-specific protocols (MQTT, CoAP, Zigbee, etc.)
- Identify security vulnerabilities in network traffic
- Analyze protocol distribution
- Find unencrypted communications
- Detect weak authentication mechanisms
- Identify insecure IoT device behaviors
Instructions
When the user asks to analyze network traffic, capture IoT traffic, or assess network security:
1. **Determine input type**:
- PCAP file analysis (offline)
- Live network capture (requires interface)
2. **Gather requirements**:
- For PCAP: Get file path(s)
- For live capture: Get network interface name and duration
- Ask about filtering needs (specific IPs, protocols)
- Check if custom detection rules are needed
3. **Execute the analysis**:
- Use the iotnet command from the iothackbot bin directory
Usage Modes
PCAP Analysis (Offline)
Analyze one or more existing packet capture files:
iotnet capture1.pcap capture2.pcap
Live Capture
Capture and analyze traffic in real-time:
sudo iotnet -i eth0 -d 30
Parameters
**Input Options:**
- `pcap_files`: One or more PCAP files to analyze
- `-i, --interface`: Network interface for live capture
**Filtering Options:**
- `--ip`: Filter traffic by IP address
- `-c, --capture-filter`: BPF syntax filter for live capture
- `--display-filter`: Wireshark display filter for PCAP analysis
**Live Capture Options:**
- `-d, --duration`: Capture duration in seconds (default: 30)
**Analysis Options:**
- `--config`: Custom IoT detection rules configuration file
- Default: `config/iot/detection_rules.json` in the iothackbot directory
**Output Options:**
- `--format text|json|quiet`: Output format (default: text)
- `-v, --verbose`: Detailed output
Examples
Analyze 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"
Detected IoT Protocols
The tool can identify:
- **MQTT**: Message Queue Telemetry Transport
- **CoAP**: Constrained Application Protocol
- **Zigbee**: Low-power mesh networking
- **Z-Wave**: Home automation protocol
- **ONVIF**: IP camera protocol
- **UPnP/SSDP**: Universal Plug and Play
- **Modbus**: Industrial control protocol
- And many more (configurable)
Security Checks
IoTNet identifies vulnerabilities such as:
- Unencrypted MQTT traffic
- Missing TLS/encryption
- Weak or no authentication
- Plaintext credentials
- Insecure protocol versions
- Known vulnerable implementations
Output Information
Results include:
- **Total packets analyzed**
- **Protocol distribution** with percentages
- **IoT findings** with protocol details and packet info
- **Vulnerabilities** with severity levels (high/medium/low)
- **Recommendations** for remediation
Important Notes
- Live capture requires root/sudo privileges
- Requires network access to specified interface
- PCAP analysis does not require elevated privileges
- Detection rules can be customized in config file
- Supports standard PCAP format from tcpdump, Wireshark, etc.
Read more
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.
IoTNet - IoT Network Traffic Analyzer
You are helping the user analyze network traffic to detect IoT protocols and identify security vulnerabilities using the iotnet tool.
Tool Overview
IoTNet analyzes network packet captures (PCAPs) or performs live traffic capture to:
- Detect IoT-specific protocols (MQTT, CoAP, Zigbee, etc.)
- Identify security vulnerabilities in network traffic
- Analyze protocol distribution
- Find unencrypted communications
- Detect weak authentication mechanisms
- Identify insecure IoT device behaviors
Instructions
When the user asks to analyze network traffic, capture IoT traffic, or assess network security:
1. **Determine input type**:
- PCAP file analysis (offline)
- Live network capture (requires interface)
2. **Gather requirements**:
- For PCAP: Get file path(s)
- For live capture: Get network interface name and duration
- Ask about filtering needs (specific IPs, protocols)
- Check if custom detection rules are needed
3. **Execute the analysis**:
- Use the iotnet command from the iothackbot bin directory
Usage Modes
PCAP Analysis (Offline)
Analyze one or more existing packet capture files:
iotnet capture1.pcap capture2.pcap
Live Capture
Capture and analyze traffic in real-time:
sudo iotnet -i eth0 -d 30
Parameters
**Input Options:**
- `pcap_files`: One or more PCAP files to analyze
- `-i, --interface`: Network interface for live capture
**Filtering Options:**
- `--ip`: Filter traffic by IP address
- `-c, --capture-filter`: BPF syntax filter for live capture
- `--display-filter`: Wireshark display filter for PCAP analysis
**Live Capture Options:**
- `-d, --duration`: Capture duration in seconds (default: 30)
**Analysis Options:**
- `--config`: Custom IoT detection rules configuration file
- Default: `config/iot/detection_rules.json` in the iothackbot directory
**Output Options:**
- `--format text|json|quiet`: Output format (default: text)
- `-v, --verbose`: Detailed output
Examples
Analyze 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"
Detected IoT Protocols
The tool can identify:
- **MQTT**: Message Queue Telemetry Transport
- **CoAP**: Constrained Application Protocol
- **Zigbee**: Low-power mesh networking
- **Z-Wave**: Home automation protocol
- **ONVIF**: IP camera protocol
- **UPnP/SSDP**: Universal Plug and Play
- **Modbus**: Industrial control protocol
- And many more (configurable)
Security Checks
IoTNet identifies vulnerabilities such as:
- Unencrypted MQTT traffic
- Missing TLS/encryption
- Weak or no authentication
- Plaintext credentials
- Insecure protocol versions
- Known vulnerable implementations
Output Information
Results include:
- **Total packets analyzed**
- **Protocol distribution** with percentages
- **IoT findings** with protocol details and packet info
- **Vulnerabilities** with severity levels (high/medium/low)
- **Recommendations** for remediation
Important Notes
- Live capture requires root/sudo privileges
- Requires network access to specified interface
- PCAP analysis does not require elevated privileges
- Detection rules can be customized in config file
- Supports standard PCAP format from tcpdump, Wireshark, etc.
Open-source IoT security testing toolkit with integrated Claude Code skills for automated vulnerability discovery.
Other skills on iothackbot.
- /apktool
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.
Open skill - /chipsec
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
Open skill - /ffind
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.
Open skill - /jadx
Android APK decompiler that converts DEX bytecode to readable Java source code. Use when you need to decompile APK files, analyze app logic, search for vulnerabilities, find hardcoded credentials, or understand app behavior through readable source code.
Open skill - /jtagprobe
Probe IoT/embedded targets for exposed SWD/JTAG debug interfaces using a SEGGER J-Link. Detects whether debug is OPEN, LOCKED (readout-protected), or DEAD (fused off). Use when assessing whether a target's on-chip debug port can be reached, identifying the silicon vendor from
Open skill - /logicmso
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.
Open skill

