iotaudit
Is your smart pet feeder, camera or plug safe? iotaudit watches what your own IoT devices
do on the network and gives each one an A–F grade with a one-page HTML report. Everything
runs locally: no account, no telemetry, no cloud.
It answers the questions you actually have about a cheap smart device:
- Who does it talk to? Domains (DNS + TLS SNI + HTTP Host), IPs, country, organisation.
- Is it encrypted? Plaintext HTTP, unencrypted TCP, old TLS, or "custom" high-entropy protocols.
- What ports are open? Optional
nmapscan with risk notes (telnet, RTSP, UPnP, ADB, …). - Does it phone home while idle? Idle-upload check and a traffic timeline with bursts.
- Where did the video go? LAN peer (phone P2P) vs cloud vs STUN/TURN — and an honest note when a stream was set up but never actually passed through your computer.
Status: 0.1.0. Hotspot + ARP capture, pcap analysis, IPv6/NDP, grading, HTML report and the MCP server work. CVE lookup and UPnP checks are on the roadmap.
Sample report
A report for a Tuya-associated pet feeder (anonymized). It talks to US clouds over TLS/MQTT, keeps telnet open, uses hardcoded 8.8.8.8, sets up a P2P video session that was not observed on this run, and shows an odd special-use "LAN peer" that is not a real device:
Open docs/sample-report.html in a browser for the full version.
Install
# from source (PyPI release prepared via Trusted Publishing, not yet live)
pipx install "git+https://github.com/emirmrkaljevic/iotaudit"
# or, with the MCP server + geo extras:
pip install "iotaudit[mcp] @ git+https://github.com/emirmrkaljevic/iotaudit"
Capturing needs root (sudo). The optional port scan needs nmap.
Quickstart
macOS
brew install nmap
pipx install "git+https://github.com/emirmrkaljevic/iotaudit"
# Just run it: pick your device from the list, then leave it alone (or use its app).
sudo "$(which iotaudit)" capture --mode arp --i-own-this-network
iotaudit scans your LAN, lists devices (IP, MAC, vendor; Tuya/Espressif flagged as likely IoT),
and lets you pick one. It then ARP-spoofs only that device so its traffic flows through your
Mac, captures for up to an hour (Ctrl+C stops early and still writes the report), and restores the
ARP tables and IP-forwarding on exit. With a device picked, --watch-lan (phone P2P) and the
IPv6/NDP filter are on by default.
Linux
sudo apt install nmap
pipx install "git+https://github.com/emirmrkaljevic/iotaudit"
# Same ARP flow as macOS:
sudo "$(which iotaudit)" capture --mode arp --i-own-this-network
# Or hotspot mode: your laptop becomes an AP; re-pair the device to it (needs NetworkManager).
sudo iotaudit capture --mode hotspot --iface wlan0 --ssid iotaudit --password 'choose-a-pass' \
--device 10.42.0.50 --scan --out feeder.html
Analyse an existing capture
# from Wireshark, your router, or OpenWrt `tcpdump -w`
iotaudit analyze capture.pcap --device 192.168.1.50 --json results.json --out report.html
The report lands at ./iotaudit-report.html with a matching .json next to it.
IPv6, P2P video, and "not observed"
Live video from a camera or feeder often does not go to the cloud — it goes directly to your
phone over the local Wi-Fi (P2P), after a short STUN/TURN handshake. iotaudit tries hard to see
that stream (--watch-lan spoofs device↔phone, and the capture filter now includes IPv6 and NDP),
but two Wi-Fi clients can talk without their traffic ever passing through your computer —
because of Access-Point client isolation, a phone ignoring the spoof, or the stream riding IPv6
link-local (fe80::). When that happens the report says so honestly:
Live video set up but not observed here — the session was negotiated (STUN) but no sustained stream was captured; it most likely went straight to your phone. Not observed ≠ not happening.
For ground truth, capture at the router instead. --ipv6-ndp (experimental) also NDP-spoofs IPv6
link-local pairs.
MCP server
iotaudit-mcp # exposes audit tools to a local assistant ("audit my pet feeder")
Consent & scope
iotaudit only audits your own network. It refuses non-private targets and requires
--i-own-this-network (or an interactive I OWN THIS NETWORK confirmation). ARP/NDP spoofing on a
network you do not own may be illegal.
Findings are indicators based on observed traffic, not proof of wrongdoing by any vendor. IP geolocation by DB-IP. MIT licensed.
Metadata
Release files for iotaudit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| iotaudit-0.1.0.tar.gz | 5.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iotaudit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.2 MB
Release files / iotaudit-0.1.0.tar.gz
| Download URL | iotaudit-0.1.0.tar.gz |
|---|---|
| Size | 5.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb03d0dc88fa69a3de0cb3c52f76270a14cbb37dc8769bd9b73b191da28a79e9
|
|
BLAKE2b-256 checksum How to use checksums |
4071ca58a1407733a16c233356b00f042cf660b85b6a8bea31bec0d17017a64e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / iotaudit-0.1.0-py3-none-any.whl
| Download URL | iotaudit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
689db2c6480ef7d14dff7a6988244ee4e6a237324145d63a029c51cdc8565e6a
|
|
BLAKE2b-256 checksum How to use checksums |
b324771a98758e3906024e59db8a6d74c024eb4511d49c910bac92a40fc45912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency log