agentleFS
BrownFineSecurityBrownFineSecurity/iothackbot/skills/onvifscan/SKILL.md

onvifscan

Skill847 starsChanged 5 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test for unauthenticated access to ONVIF endpoints

    line 13
  2. Distinctive:

    When the user asks to scan ONVIF devices, test IP cameras, or assess IoT device security:

    line 18
  3. Distinctive:

    Ask for the device URL/IP

    line 25
  4. Distinctive:

    Check if they have custom wordlists

    line 27
  5. Very specific:

    Use the onvifscan command from the iothackbot bin directory

    line 30
  6. Very specific:

    Use -a flag with caution - may test destructive endpoints

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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:

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:

onvifscan auth 192.168.1.100

Auth check with verbose output:

onvifscan auth http://192.168.1.100:8080 -v

Brute force with custom wordlists:

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.