CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offensive-iot

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security
High

W008: Secret detected in skill content (API keys, tokens, passwords).

What this means

Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.

Why it was flagged

The skill document contains no API keys, private keys, tokens, or account passwords. The `<potential_matches>` section is empty. The `root/<serial number>`, `admin/admin`, and `IoTLab` strings are default-credential guidance or setup names, so they are ignored under the low-entropy rules. Line 285 contains the literal hex value `0x9F5595F10257C8A469CBF42BC93FEE31`, a 128-bit Touchlink master key. It is high-entropy, hardcoded, and usable in an attack chain. It is also a published Zigbee specification constant that appears in public research, so it is not a credential tied to any live account or service. Under the recall-first directive, I am flagging it because it is a literal key value that enables decryption of commissioning traffic, which falls within the secret-exposure risk category. Reviewers may reasonably downgrade it to a public protocol constant. No other lines contain high-entropy secret material.

Report incorrect finding
Medium

W013: Attempt to modify system services in skill instructions.

What this means

The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.

Why it was flagged

The skill is a dual-use offensive IoT testing methodology that mostly targets external devices, but it explicitly instructs the agent to run a `sudo create_ap` command that reconfigures the local machine's network to host a rogue access point, plus a transparent MITM proxy setup, which falls under the sudo-and-system-modification concern.

Repository

SnailSploit/Claude-Red

Path

Skills/iot/offensive-iot/SKILL.md

Audited
Security analysis
Snyk

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.