Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
sparkplugFuzzer — Fuzzer for the Sparkplug B IIoT protocol | Kitploit
Tools/GitHubGitHub/bishopfox/sparkplugfuzzer
Dynamic Analysis (Sandboxing)IoT SecurityVulnerability AnalysisSCADA/ICS SecurityFuzzingNetwork SecurityPenetration TestingAuthentication
GitHubbishopfox/sparkplugfuzzer

sparkplugFuzzer

Fuzzer for the Sparkplug B IIoT protocol

View Repository
1755 months agoNot yet reviewed
Share

Sparkplug B MQTT Security Fuzzer

A comprehensive security assessment tool for testing Sparkplug B MQTT protocol implementations. The fuzzer systematically tests all protocol fields across all 9 message types, discovers live devices on the network, and produces detailed logs for analysis.

Responsible Use

This tool sends malformed, injection, and protocol-violating MQTT messages to a target broker. Only run it against systems you own or have explicit written authorization to test. Sparkplug B brokers commonly sit in OT/ICS environments where unexpected payloads can disrupt physical processes — assume every target is production-adjacent unless proven otherwise.

If you discover a vulnerability in a Sparkplug B implementation using this tool, please follow coordinated disclosure with the affected vendor. To report a security issue in this tool itself, see SECURITY.md.

Table of Contents

  • Overview
  • Prerequisites
  • Installation
  • Quick Start
  • Usage
    • Command-Line Options
    • Fuzz Categories
    • Examples
  • How It Works
    • Execution Flow
    • Network Discovery
    • Authentication Assessment
    • Targeted Fuzzing
  • Running the tests
  • Output and Log Analysis
    • Log Format
    • Analyzing Results
  • Protocol Coverage
    • Message Types
    • Data Types
    • Field Coverage
  • Architecture

Overview

The Sparkplug B specification defines a topic namespace and payload format built on MQTT and Google Protocol Buffers for Industrial IoT (IIoT) environments. This fuzzer assesses the security and robustness of Sparkplug B implementations by:

  • Testing all 19 metric data types with boundary values and overflow conditions
  • Injecting malicious strings (XSS, SQLi, format strings, path traversal, command injection)
  • Creating type mismatches between declared datatypes and actual protobuf value fields
  • Violating protocol state machine ordering (data before birth, double births, data after death)
  • Corrupting serialized protobuf payloads at the binary level
  • Spoofing birth/death certificates for discovered network devices
  • Fuzzing MQTT topic namespaces with special characters, case variations, and structural violations

Prerequisites

  • Python 3.8+
  • MQTT Broker — the target system under test (e.g., Mosquitto, HiveMQ, EMQX, or any Sparkplug B aware broker)
  • Authorization — this tool is intended for authorized security testing only

Installation

On modern Debian/Ubuntu/Kali (PEP-668 systems), --setup cannot pip install into the system Python — use a virtual environment or pipx first. The recommended path:

python3 -m venv .venv
source .venv/bin/activate
python3 sparkplug-fuzzer.py --setup

Or run via pipx run if you prefer not to manage the venv yourself. On older systems without PEP-668 enforcement, plain python3 sparkplug-fuzzer.py --setup works directly.

--setup will:

  1. Install pip dependencies (paho-mqtt, protobuf)
  2. Clone a pinned tag of the Eclipse Tahu repository (see TAHU_REF in the script)
  3. Copy sparkplug_b.py and array_packer.py helper modules
  4. Compile sparkplug_b.proto into Python bindings (uses protoc if available, falls back to grpcio-tools)
  5. Clean up the Tahu clone

After setup, your directory should contain:

sparkplug-fuzzer.py     # The fuzzer
sparkplug_b.py          # Sparkplug B helper module (from Tahu)
array_packer.py         # Array packing helper (from Tahu)
sparkplug_b_pb2.py      # Generated protobuf bindings
requirements.txt        # Python dependencies
Manual setup (if --setup doesn't work)
pip install -r requirements.txt
git clone https://github.com/eclipse/tahu.git
cp tahu/python/core/sparkplug_b.py .
cp tahu/python/core/array_packer.py .
protoc --python_out=. sparkplug_b.proto
rm -rf tahu

Quick Start

python3 sparkplug-fuzzer.py --setup              # first-time setup
python3 sparkplug-fuzzer.py -H localhost -p 1883 -v  # run fuzzer

This will:

  1. Connect to the broker at localhost:1883
  2. Listen for 10 seconds to discover existing Sparkplug devices
  3. Establish the fuzzer as a Sparkplug node/device
  4. Run all 12 fuzz categories (~635+ test cases)
  5. Target any discovered devices with spoofed messages
  6. Write results to sparkplug_fuzz.jsonl

Usage

Command-Line Options

python3 sparkplug-fuzzer.py [OPTIONS]
OptionDefaultDescription
-H, --hostlocalhostMQTT broker hostname or IP
-p, --port1883 (or 8883 with --tls)MQTT broker port
-u, --usernameNoneMQTT username (also reads MQTT_USERNAME env var)
-P, --passwordNoneMQTT password (also reads MQTT_PASSWORD; pass - to read from stdin without echo)
--tlsoffConnect over TLS; default port becomes 8883 if -p unset
--cafileNoneCA bundle for TLS server certificate verification
--insecureoffSkip TLS hostname/certificate verification (testing only)
-g, --groupSparkplug B DevicesSparkplug group ID the fuzzer registers under
-n, --nodeFuzzNodeSparkplug edge node ID for the fuzzer
-d, --deviceFuzzDeviceSparkplug device ID for the fuzzer
-c, --categoriesallSpace-separated list of fuzz categories to run
--discovery-time10Seconds to passively listen for network discovery
--delay0.1Delay in seconds between fuzz messages
--probe-anon-writeoffDuring discovery, send one QoS=1 publish to confirm whether the broker accepts unauthenticated PUBLISH
-l, --logsparkplug_fuzz.jsonlOutput log file name (relative paths land inside --output-dir; absolute paths are honored as-is)
--output-dir./sparkplug-runs/<UTC-ts>_<host>/Per-run output directory. Created if absent.
-v, --verbose0Increase console verbosity (-v = info, -vv = debug). -vv also surfaces fuzz-generator skips, and the throttled paho.mqtt logger bumps to INFO/DEBUG with verbosity.
--setup—Install all dependencies and exit
--tahu-path—Path to a local clone of eclipse/tahu (or its python/core directory). Used by --setup in air-gapped environments instead of git clone.
--extra-string-payloads—Path to a file of additional string-injection payloads (one per line, UTF-8). Appended to the built-in STRING_FUZZ_VALUES; does not replace them. Max 10 MB / 10,000 payloads. See Custom string corpora.

Fuzz Categories

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    256

Explore all tools

Browse our collection of tools

View all tools →