onvifscan
ONVIF device security scanner for testing authentication and brute-forcing credentials. Use when you need to assess security of IP cameras or ONVIF-enabled devices.
Works with
--- name: onvifscan description: ONVIF device security scanner for testing authentication and brute-forcing credentials. Use when you need to assess security of IP cameras or ONVIF-enabled devices. license: MIT --- # Onvifscan - ONVIF Security Scanner You are helping the user scan ONVIF devices for security issues including authentication bypasses and weak credentials using the onvifscan tool. ## Tool Overview Onvifscan is an ONVIF device security scanner that can: - Test for unauthenticated access to ONVIF endpoints - Perform credential brute-forcing attacks ## Instructions When the user asks to scan ONVIF devices, test IP cameras, or assess IoT device security: 1. **Determine scan type**: - `auth`: Authentication and access control testing (recommended to start) - `brute`: Credential brute-forcing on password-protected endpoints 2. **Get target information**: - Ask for the device URL/IP - Determine which scan type to run - Check if they have custom wordlists 3. **Execute the scan**: - Use the onvifscan command from the iothackbot bin directory - Format: `onvifscan <subcommand> <url> [options]` ## Subcommands ### Auth Scan Tests ONVIF endpoints for authentication requirements: ```bash onvifscan auth http://192.168.1.100 ``` Options: - `-v, --verbose`: Show full XML responses - `-a, --all`: Test ALL endpoints including potentially destructive ones - `--format text|json|quiet`: Output format ### Brute Force Attempts credential brute-forcing on protected endpoints: ```bash onvifscan brute http://192.168.1.100 ``` Options: - `--usernames <file>`: Custom usernames wordlist (default: built-in onvif-usernames.txt) - `--passwords <file>`: Custom passwords wordlist (default: built-in onvif-passwords.txt) - `--format text|json|quiet`: Output format ## Examples Quick auth check on a device: ```bash onvifscan auth 192.168.1.100 ``` Auth check with verbose output: ```bash onvifscan auth http://192.168.1.100:8080 -v ``` Brute force with custom wordlists: ```bash onvifscan brute 192.168.1.100 --usernames custom-users.txt --passwords custom-pass.txt ``` ## Important Notes - URLs can omit `http://` - it will be added automatically - Auth scan is non-destructive and safe to run - Use `-a` flag with caution - may test destructive endpoints - Brute force is rate-limited to prevent device overload (max 20 attempts by default) - Built-in wordlists located in `wordlists/` directory
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

