iotnet
Skill847 starsChanged 5 months agoMITView on GitHub
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.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
When the user asks to analyze network traffic, capture IoT traffic, or assess network security:
- Distinctive: line 31
Ask about filtering needs (specific IPs, protocols)
- Distinctive: line 32
Check if custom detection rules are needed
- Very specific: line 35
Use the iotnet command from the iothackbot bin directory
- Very specific: line 67
Default: config/iot/detection_rules.json in the iothackbot directory
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Determine input type:
- PCAP file analysis (offline)
- Live network capture (requires interface)
- 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
- 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.pcapLive Capture
Capture and analyze traffic in real-time:
sudo iotnet -i eth0 -d 30Parameters
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.jsonin the iothackbot directory
- Default:
Output Options:
--format text|json|quiet: Output format (default: text)-v, --verbose: Detailed output
Examples
Analyze a packet capture file:
iotnet /path/to/capture.pcapLive capture for 60 seconds on wifi interface:
sudo iotnet -i wlan0 -d 60Analyze traffic for specific IP:
iotnet capture.pcap --ip 192.168.1.100Live capture with BPF filter:
sudo iotnet -i eth0 -c "port 1883 or port 5683" -d 45Multiple PCAPs with custom config:
iotnet file1.pcap file2.pcap --config custom-rules.jsonFilter 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

