/telnetshell
Use telnet to interact with IoT device shells for pentesting operations including device enumeration, vulnerability discovery, credential testing, and post-exploitation. Use when the user needs to interact with network-accessible shells, IoT devices, or telnet services.
$ npx -y skills add brownfinesecurity/iothackbot --skill telnetshell --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/telnetshell
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use telnet to interact with IoT device shells for pentesting operations including device enumeration, vulnerability discovery, credential testing, and post-exploitation. Use when the user needs to interact with network-accessible shells, IoT devices, or telnet services.
SKILL.md
telnetshell.SKILL.mdname: telnetshell
description: Use telnet to interact with IoT device shells for pentesting operations including device enumeration, vulnerability discovery, credential testing, and post-exploitation. Use when the user needs to interact with network-accessible shells, IoT devices, or telnet services.
IoT Telnet Shell (telnetshell)
This skill enables interaction with IoT device shells accessible via telnet for security testing and penetration testing operations. It supports unauthenticated shells, weak authentication testing, device enumeration, and post-exploitation activities.
Prerequisites
- Python 3 with pexpect library (`pip install pexpect` or `sudo pacman -S python-pexpect`)
- telnet client installed on the system (`sudo pacman -S inetutils` on Arch)
- Network access to the target device's telnet port
Recommended Approach: Telnet Helper Script
**IMPORTANT**: This skill includes a Python helper script (`telnet_helper.py`) that provides a clean, reliable interface for telnet communication. **This is the RECOMMENDED method** for interacting with IoT devices.
Default Session Logging
**ALL commands run by Claude will be logged to `/tmp/telnet_session.log` by default.**
To observe what Claude is doing in real-time:
# In a separate terminal, run:
tail -f /tmp/telnet_session.log
This allows you to watch all telnet I/O as it happens without interfering with the connection.
Why Use the Telnet Helper?
The helper script solves many problems with direct telnet usage:
- **Clean output**: Automatically removes command echoes, prompts, and ANSI codes
- **Prompt detection**: Automatically detects and waits for device prompts
- **Timeout handling**: Proper timeout management with no arbitrary sleeps
- **Easy scripting**: Simple command-line interface for single commands or batch operations
- **Session logging**: All I/O logged to `/tmp/telnet_session.log` for observation
- **Reliable**: No issues with TTY requirements or background processes
- **JSON output**: For programmatic parsing and tool chaining
Quick Start with Telnet Helper
**Single Command:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "uname -a"
**Custom Port:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --port 2222 --command "ls /"
**With Custom Prompt (recommended for known devices):**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --prompt "^/ [#\$]" --command "ifconfig"
**Interactive Mode:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --port 2222 --interactive
**Batch Commands from File:**
# Create a file with commands (one per line)
echo -e "uname -a\ncat /proc/version\nifconfig\nps" > commands.txt
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --script commands.txt
**JSON Output (for parsing):**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "uname -a" --json
**Debug Mode:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "ls" --debug
**Session Logging (for observation):**
# Terminal 1 - Run with logging
python3 .claude/skills/telnetshell/telnet_helper.py \
--host 192.168.1.100 \
--port 2222 \
--logfile /tmp/session.log \
--interactive
# Terminal 2 - Watch the session in real-time
tail -f /tmp/session.log
**Note:** See `OBSERVING_SESSIONS.md` for comprehensive guide on monitoring telnet sessions.
See [examples.md](examples.md) for full worked walkthroughs: initial device identification, BusyBox detection, full system enumeration, SUID hunting, and hardcoded-credential discovery.
Telnet Helper Options
Required (one of):
--command, -c CMD Execute single command
--interactive, -i Enter interactive mode
--script, -s FILE Execute commands from file
Connection Options:
--host, -H HOST Target host IP or hostname (required)
--port, -P PORT Telnet port (default: 23)
--timeout, -t SECONDS Command timeout (default: 3.0)
--prompt, -p PATTERN Custom prompt regex pattern
Output Options:
--raw, -r Don't clean output (show echoes, prompts)
--json, -j Output in JSON format
--logfile, -l FILE Log all I/O to file (default: /tmp/telnet_session.log)
--debug Show debug information
Common Prompt Patterns
The helper script includes common prompt patterns, but you can specify custom ones:
# BusyBox shell (common on IoT)
--prompt "/\s*[#\$]\s*$"
# Standard root/user prompts
--prompt "^[#\$]\s*$"
# Custom device
--prompt "^MyDevice>\s*$"
# Uniview cameras
--prompt "^User@[^>]+>\s*$"
Device Enumeration Example with Telnet Helper
Here's a complete example of safely enumerating a device:
# Set variables for convenience
HELPER="python3 .claude/skills/telnetshell/telnet_helper.py"
HOST="192.168.1.100"
PORT="2222"
LOGFILE="/tmp/telnet_session.log"
# System information
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "uname -a"
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "cat /proc/version"
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "cat /proc/cpuinfo"
# Check for BusyBox
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "busybox"
# Network configuration
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "ifconfig"
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "route -n"
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "netstat -tulpn"
# Process listing (may need longer timeout)
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --timeout 5 --command "ps aux"
# File system exploration
$HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "ls -la /"
$HELPER --host
Read more
name: telnetshell description: Use telnet to interact with IoT device shells for pentesting operations including device enumeration, vulnerability discovery, credential testing, and post-exploitation. Use when the user needs to interact with network-accessible shells, IoT devices, or telnet services.
IoT Telnet Shell (telnetshell)
This skill enables interaction with IoT device shells accessible via telnet for security testing and penetration testing operations. It supports unauthenticated shells, weak authentication testing, device enumeration, and post-exploitation activities.
Prerequisites
- Python 3 with pexpect library (`pip install pexpect` or `sudo pacman -S python-pexpect`)
- telnet client installed on the system (`sudo pacman -S inetutils` on Arch)
- Network access to the target device's telnet port
Recommended Approach: Telnet Helper Script
**IMPORTANT**: This skill includes a Python helper script (`telnet_helper.py`) that provides a clean, reliable interface for telnet communication. **This is the RECOMMENDED method** for interacting with IoT devices.
Default Session Logging
**ALL commands run by Claude will be logged to `/tmp/telnet_session.log` by default.**
To observe what Claude is doing in real-time:
# In a separate terminal, run: tail -f /tmp/telnet_session.log
This allows you to watch all telnet I/O as it happens without interfering with the connection.
Why Use the Telnet Helper?
The helper script solves many problems with direct telnet usage:
- **Clean output**: Automatically removes command echoes, prompts, and ANSI codes
- **Prompt detection**: Automatically detects and waits for device prompts
- **Timeout handling**: Proper timeout management with no arbitrary sleeps
- **Easy scripting**: Simple command-line interface for single commands or batch operations
- **Session logging**: All I/O logged to `/tmp/telnet_session.log` for observation
- **Reliable**: No issues with TTY requirements or background processes
- **JSON output**: For programmatic parsing and tool chaining
Quick Start with Telnet Helper
**Single Command:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "uname -a"
**Custom Port:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --port 2222 --command "ls /"
**With Custom Prompt (recommended for known devices):**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --prompt "^/ [#\$]" --command "ifconfig"
**Interactive Mode:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --port 2222 --interactive
**Batch Commands from File:**
# Create a file with commands (one per line) echo -e "uname -a\ncat /proc/version\nifconfig\nps" > commands.txt python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --script commands.txt
**JSON Output (for parsing):**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "uname -a" --json
**Debug Mode:**
python3 .claude/skills/telnetshell/telnet_helper.py --host 192.168.1.100 --command "ls" --debug
**Session Logging (for observation):**
# Terminal 1 - Run with logging python3 .claude/skills/telnetshell/telnet_helper.py \ --host 192.168.1.100 \ --port 2222 \ --logfile /tmp/session.log \ --interactive # Terminal 2 - Watch the session in real-time tail -f /tmp/session.log
**Note:** See `OBSERVING_SESSIONS.md` for comprehensive guide on monitoring telnet sessions.
See [examples.md](examples.md) for full worked walkthroughs: initial device identification, BusyBox detection, full system enumeration, SUID hunting, and hardcoded-credential discovery.
Telnet Helper Options
Required (one of): --command, -c CMD Execute single command --interactive, -i Enter interactive mode --script, -s FILE Execute commands from file Connection Options: --host, -H HOST Target host IP or hostname (required) --port, -P PORT Telnet port (default: 23) --timeout, -t SECONDS Command timeout (default: 3.0) --prompt, -p PATTERN Custom prompt regex pattern Output Options: --raw, -r Don't clean output (show echoes, prompts) --json, -j Output in JSON format --logfile, -l FILE Log all I/O to file (default: /tmp/telnet_session.log) --debug Show debug information
Common Prompt Patterns
The helper script includes common prompt patterns, but you can specify custom ones:
# BusyBox shell (common on IoT) --prompt "/\s*[#\$]\s*$" # Standard root/user prompts --prompt "^[#\$]\s*$" # Custom device --prompt "^MyDevice>\s*$" # Uniview cameras --prompt "^User@[^>]+>\s*$"
Device Enumeration Example with Telnet Helper
Here's a complete example of safely enumerating a device:
# Set variables for convenience HELPER="python3 .claude/skills/telnetshell/telnet_helper.py" HOST="192.168.1.100" PORT="2222" LOGFILE="/tmp/telnet_session.log" # System information $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "uname -a" $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "cat /proc/version" $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "cat /proc/cpuinfo" # Check for BusyBox $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "busybox" # Network configuration $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "ifconfig" $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "route -n" $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "netstat -tulpn" # Process listing (may need longer timeout) $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --timeout 5 --command "ps aux" # File system exploration $HELPER --host $HOST --port $PORT --logfile "$LOGFILE" --command "ls -la /" $HELPER --host
Open-source IoT security testing toolkit with integrated Claude Code skills for automated vulnerability discovery.
Other skills on iothackbot.
- /apktool
Android APK unpacking and resource extraction tool for reverse engineering. Use when you need to decode APK files, extract resources, examine AndroidManifest.xml, analyze smali code, or repackage modified APKs.
Open skill - /chipsec
Static analysis of UEFI/BIOS firmware dumps using Intel's chipsec framework. Decode firmware structure, detect known malware and rootkits (LoJax, ThinkPwn, HackingTeam, MosaicRegressor), generate EFI executable inventories with hashes, extract NVRAM variables, and parse SPI
Open skill - /ffind
Advanced file finder with type detection and filesystem extraction for analyzing firmware and extracting embedded filesystems. Use when you need to analyze firmware files, identify file types, or extract ext2/3/4 or F2FS filesystems.
Open skill - /iotnet
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.
Open skill - /jadx
Android APK decompiler that converts DEX bytecode to readable Java source code. Use when you need to decompile APK files, analyze app logic, search for vulnerabilities, find hardcoded credentials, or understand app behavior through readable source code.
Open skill - /jtagprobe
Probe IoT/embedded targets for exposed SWD/JTAG debug interfaces using a SEGGER J-Link. Detects whether debug is OPEN, LOCKED (readout-protected), or DEAD (fused off). Use when assessing whether a target's on-chip debug port can be reached, identifying the silicon vendor from
Open skill

