Skills nikto
install
source · Clone the upstream repo
git clone https://github.com/TerminalSkills/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/TerminalSkills/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/nikto" ~/.claude/skills/terminalskills-skills-nikto && rm -rf "$T"
manifest:
skills/nikto/SKILL.mdsafety · automated scan (low risk)
This is a pattern-based risk scan, not a security review. Our crawler flagged:
- references .env files
Always read a skill's source content before installing. Patterns alone don't mean the skill is malicious — but they warrant attention.
source content
Nikto
Overview
Nikto is a web server scanner that checks for 7,000+ potentially dangerous files, outdated server versions, version-specific problems, and server configuration issues. It's noisy (not stealthy) but comprehensive — catches misconfigurations, default files, exposed admin interfaces, and known vulnerable components that automated scanners often miss.
Instructions
Step 1: Basic Scan
# Scan a web server nikto -h https://target.example.com # Checks: # - Server version and known CVEs # - Dangerous HTTP methods (PUT, DELETE, TRACE) # - Default files (/phpinfo.php, /server-status, /.env) # - Directory indexing # - Missing security headers # - Outdated components # Scan specific port nikto -h target.example.com -p 8080 # Scan multiple ports nikto -h target.example.com -p 80,443,8080,8443 # Scan with SSL nikto -h https://target.example.com -ssl
Step 2: Tuning and Targeting
# Tune scan to specific check categories nikto -h https://target.example.com -Tuning 123456789abcde # 1: Interesting file / seen in logs # 2: Misconfiguration / default file # 3: Information disclosure # 4: Injection (XSS/Script/HTML) # 5: Remote file retrieval (inside web root) # 6: Denial of service (skip in production) # 7: Remote file retrieval (server-wide) # 8: Command execution / remote shell # 9: SQL injection # a: Authentication bypass # b: Software identification # c: Remote source inclusion # d: WebService # e: Admin console # Only check for misconfigurations and info disclosure nikto -h https://target.example.com -Tuning 23 # Use a specific wordlist for CGI directories nikto -h https://target.example.com -Cgidirs "all" # Authenticated scanning nikto -h https://target.example.com \ -id admin:password123 # or with cookie nikto -h https://target.example.com \ -cookie "session=abc123; token=xyz789"
Step 3: Output and Integration
# Save results in multiple formats nikto -h https://target.example.com -o nikto-report.html -Format html nikto -h https://target.example.com -o nikto-report.xml -Format xml nikto -h https://target.example.com -o nikto-report.csv -Format csv # JSON output for automation nikto -h https://target.example.com -o nikto-report.json -Format json # Scan targets from Nmap output nmap -sV -p 80,443,8080 -oG - 192.168.1.0/24 | \ grep "open" | awk '{print $2}' | \ while read ip; do nikto -h $ip -o "nikto-$ip.html" -Format html; done
Guidelines
- Nikto is loud — it sends thousands of requests. Don't use it for stealth assessments.
- Run Nikto early in the assessment — it catches low-hanging fruit (default files, misconfigs).
- Check tuning categories:
for quick misconfiguration scan, full scan for thorough assessment.-Tuning 23 - Combine with Nmap: scan ports first, then run Nikto against discovered web servers.
- XML/JSON output integrates with reporting tools and vulnerability management platforms.
- False positives are common — verify each finding manually before including in the report.
- Run with
to check CGI directories for legacy vulnerabilities (ShellShock, etc.).-Cgidirs all - Nikto is complementary to Burp Suite — Nikto checks server config, Burp tests application logic.