Repository navigation
Scripts
Runtime status: The historical collection includes Python 2 examples and an unfinished Go sketch. Listing a script here does not certify that it runs on a current system.
Legacy script collection: Cypherpunk toolkit review provides safe source attribution and Python 2 โ Python 3 modernization cautions. It does not add third-party executables or payloads.
Documentation references: Curated technical docs links to GitHub Docs, Git tutorials, and Go by Example for script review and maintenance; prefer vendor docs for current syntax.
Secret and dependency checks: OpenSSF Scorecard, Gitleaks, Syft and OSV supply-chain workflow explains versioned inspection and evidence handling for the scripts collection; source code is not automatically safe because it is published.
| Resource | Description |
|---|---|
| Bash Cheat Sheet | Shell syntax and reusable patterns |
| CLI Field Commands | Everyday command-line reference |
| Reviewed Reference Index | Cross-section cheat sheets |
| Tool Pinning Policy | Version and dependency controls |
| Curated Rubber Ducky GitHub Projects | Popular official/community source libraries, GitHub popularity, firmware compatibility and code-review boundaries |
| Curated Bash Bunny GitHub Projects | Official/legacy repositories, archived-status checks, helper compatibility and lab review workflow |
| Hak5 Payload Formats & Sideload Checks | Cross-device Pager, Mark VII, Bash Bunny, Ducky, Shark Jack, Packet Squirrel and Key Croc runtime distinctions |
| WiFi Pineapple Pager | User/Recon/Alert payloads, event handling, controlled installation and rollback |
| Mark VII Campaign Examples | Five monitored/restricted client wireless assessment runbooks |
Inspect provenance and source before running downloaded scripts.
Collection of security automation scripts, exploitation tools, and utility programs
Part of the ULTIMATE CYBERSECURITY MASTER GUIDE
External script sourcing: Curated security GitHub collections describe useful upstream projects; no linked payload is automatically vetted or installed.
- Overview
- Script Categories
- Directory Structure
- How to Use These Scripts
โ ๏ธ CRITICAL Security & Legal Warning- Contributing
- Resources
The folder-level index for every automation script in the repository (Bash, C, Go, PowerShell, Python, SQL, YAML) - the only file that explains directory layout and legal warnings once, instead of repeating them in every language subfolder's own README.
Covers directory structure, script categories by language, usage instructions, the critical legal warning, contributing guidelines, and quick links/resources. Differs from Scripts/Bash/BashBunny/README.md, Scripts/Bash/bash_scripting_cheat-sheet.md, and Scripts/Ducky/README.md, which document a specific script collection or reference topic rather than the folder as a whole. The published repository includes executable scripts in these directories; do not infer availability or safety from a partial local checkout. Review legacy archive dispositions separately.
A reader can find the right script for a task by category/language and understands the legal authorization requirement before running anything.
When looking for an existing script before writing a new one, or when unsure what legal/usage constraints apply to this folder's contents.
This directory contains security automation scripts, penetration testing tools, and utility programs written in multiple programming languages. These scripts are designed for authorized security testing, research, and educational purposes.
This collection includes read-only utilities, active scanners, and tools that can access or change systems. For active testing, use only targets and methods within your authority and documented scope. Written approval is useful evidence of scope, but the required form and legal rules depend on the engagement and jurisdiction.
The CFAA statute defines multiple offenses with different elements and penalties; not every unauthorized or out-of-policy use of a script is automatically a federal crime. See the DOJ CFAA charging policy, which guides federal prosecutors. Other laws, contracts, privacy obligations and organizational rules may also apply.
Scripts/
โโโ Bash/ # Bash shell scripts
โโโ C/ # C programs and utilities
โโโ GO/ # Historical mixed-language collection; many Python 2 examples
โโโ PowerShell/ # PowerShell scripts (Windows)
โโโ Python/ # Python scripts and tools
โโโ SQL/ # SQL scripts and queries
โโโ YAML/ # YAML configuration files
Location: /Scripts/Bash/
Types of Scripts:
- System administration automation
- Network reconnaissance tools
- Security auditing scripts
- Log analysis utilities
- Automated exploitation frameworks
- System enumeration tools
Common Use Cases:
- Linux/Unix system administration
- Automated security testing
- Log parsing and analysis
- System monitoring
- Security auditing
Target Platforms:
- Linux distributions
- Unix-based systems
- macOS
- WSL (Windows Subsystem for Linux)
Location: /Scripts/C/
Current Programs:
| Program | Description | Purpose |
|---|---|---|
| get_user.c | User enumeration utility | System reconnaissance |
| getuser.c | User information retrieval | Privilege enumeration |
| scanner.c | Network or port scanner | Network reconnaissance |
| system_sleep.c | System sleep/suspend utility | System manipulation |
| systemsleep.c | System sleep implementation | Testing/manipulation |
Characteristics:
- Low-level system access
- High performance execution
- Direct system API calls
- Compiled executables
- Platform-specific implementations
Security Considerations:
โ ๏ธ C programs have direct system access and can:
โข Access low-level system functions
โข Bypass security controls if misused
โข Cause system instability if buggy
โข Execute with elevated privileges
โข Directly manipulate memory and processes
MUST be compiled and tested in isolated environments before use.
Location: /Scripts/PowerShell/
Current Scripts:
| Script | Description | Risk Level |
|---|---|---|
| adlogin.ps1 | Active Directory login/authentication testing | ๐ด HIGH |
| cred_hunt.ps1 | Credential hunting and discovery | ๐ด HIGH |
| localbrute.ps1 | Local account brute force tool | ๐ด HIGH |
| localbrute-extra-mini.ps1 | Compact local brute force variant | ๐ด HIGH |
| port-scan-tcp.ps1 | TCP port scanning utility | ๐ก MEDIUM |
| port-scan-tcp-compat.ps1 | Compatible TCP port scanner | ๐ก MEDIUM |
| port-scan-udp.ps1 | UDP port scanning utility | ๐ก MEDIUM |
| port_scanner.ps1 | General purpose port scanner | ๐ก MEDIUM |
| rev_shell.ps1 | Reverse shell utility | ๐ด HIGH |
| smblogin.ps1 | SMB authentication testing | ๐ด HIGH |
| smblogin-extra-mini.ps1 | Compact SMB login tester | ๐ด HIGH |
| system_enum.ps1 | System enumeration script | ๐ก MEDIUM |
Capabilities:
- Active Directory security testing
- Credential access and testing
- Network reconnaissance
- Windows system enumeration
- SMB/CIFS protocol testing
- Remote access establishment
| Resource | Description |
|---|---|
| Active Directory Checklist | Directory service assessment |
| Credential Access Checklist | Authorized credential testing boundaries |
| Windows Privilege Escalation Checklist | Windows privilege investigation |
Security Considerations:
โ ๏ธ CRITICAL: These PowerShell scripts include:
โข Credential harvesting tools (ILLEGAL without authorization)
โข Brute force attack scripts (ILLEGAL without authorization)
โข Reverse shell utilities (ILLEGAL without authorization)
โข Authentication bypass techniques
Use these scripts only on systems and accounts within your authority and documented scope. Legal consequences depend on the conduct, applicable statute and facts; see the authorization guidance above.
Location: /Scripts/Python/
Current Scripts:
| Script | Description | Risk Level |
|---|---|---|
| port_scan.py | Port scanning utility | ๐ก MEDIUM |
| port_scanner.py | Network port scanner | ๐ก MEDIUM |
| perm_scan.py | Permission scanning tool | ๐ก MEDIUM |
| perm_scan5.py | Permission scanner v5 | ๐ก MEDIUM |
| discover_network.py | Network discovery tool | ๐ก MEDIUM |
| network_attack.py | Network attack framework | ๐ด HIGH |
| proxy_test.py | Proxy testing utility | ๐ข LOW |
| Script | Description | Risk Level |
|---|---|---|
| credit_sniff.py | Credit card data sniffer | ๐ด HIGH |
| password_check.py | Password validation/testing | ๐ก MEDIUM |
| cred_sniff.py | Credential sniffing tool | ๐ด HIGH |
| ftp_sniff.py | FTP credential sniffer | ๐ด HIGH |
| Script | Description | Risk Level |
|---|---|---|
| bt-find.py | Bluetooth device discovery | ๐ก MEDIUM |
| bt_scan.py | Bluetooth scanning utility | ๐ก MEDIUM |
| blue_bug.py | Bluetooth exploitation tool | ๐ด HIGH |
| Script | Description | Risk Level |
|---|---|---|
| bsodshell.py | Blue Screen of Death exploit | ๐ด HIGH |
| conficker.py | Conficker worm-related tool | ๐ด HIGH |
| dll_inject.py | DLL injection utility | ๐ด HIGH |
| evil_batch.py | Malicious batch generator | ๐ด HIGH |
| find_ddos.py | DDoS detection/analysis | ๐ก MEDIUM |
| rev_shell.py | Reverse shell utility | ๐ด HIGH |
| Script | Description | Risk Level |
|---|---|---|
| webshell_check.py | Webshell detection tool | ๐ก MEDIUM |
| firefox_parser.py | Firefox data parser | ๐ก MEDIUM |
| imap_parser.py | IMAP protocol parser | ๐ก MEDIUM |
| link_parser.py | Link extraction tool | ๐ข LOW |
| print_cookies.py | Cookie extraction utility | ๐ก MEDIUM |
| Script | Description | Risk Level |
|---|---|---|
| geo.py | Geolocation utility | ๐ข LOW |
| geo_paint.py | Geolocation visualization | ๐ข LOW |
| google_earth_pcap.py | PCAP to Google Earth | ๐ก MEDIUM |
| google_json.py | Google JSON parser | ๐ข LOW |
| google_jsonlist.py | Google JSON list parser | ๐ข LOW |
| google_sniff.py | Google traffic sniffer | ๐ก MEDIUM |
| Script | Description | Risk Level |
|---|---|---|
| iphone_finder.py | iPhone device discovery | ๐ก MEDIUM |
| iphone_messages.py | iPhone message extraction | ๐ด HIGH |
| Script | Description | Risk Level |
|---|---|---|
| hotel_sniff.py | Hotel network sniffer | ๐ด HIGH |
| ics_find.py | Industrial Control System finder | ๐ด HIGH |
| kitten_test.py | Testing utility | ๐ข LOW |
| dup.py | Duplicate file finder | ๐ข LOW |
| dump_nmdbs.py | Database dumping tool | ๐ด HIGH |
| pdfs_paint.py | PDF visualization | ๐ข LOW |
| print_direction.py | Direction printing utility | ๐ข LOW |
| File | Description |
|---|---|
| pass.txt | Password list/dictionary |
| passout.txt | Password output file |
| nnb-cities.txt | Cities database |
Python Script Characteristics:
- Extensive network security tools
- Credential harvesting capabilities
- Exploitation frameworks
- Protocol analysis utilities
- Data exfiltration tools
- Reconnaissance utilities
Security Considerations:
โ ๏ธ EXTREME CAUTION: Python scripts include:
โข Credential sniffers (credit_sniff.py, cred_sniff.py, ftp_sniff.py)
โข Network attack tools (network_attack.py)
โข Exploitation utilities (dll_inject.py, bsodshell.py)
โข Data exfiltration tools (iphone_messages.py, dump_nmdbs.py)
โข Reverse shells (rev_shell.py)
โข ICS/SCADA targeting tools (ics_find.py)
These tools can cause:
โ Unauthorized access (federal crime)
โ Data theft (federal and state crimes)
โ Privacy violations (civil and criminal liability)
โ Network disruption (federal crime)
โ System compromise (federal crime)
โ Critical infrastructure attacks (terrorism charges possible)
USING WITHOUT AUTHORIZATION = FEDERAL PRISON TIME
Location: /Scripts/SQL/
Current Scripts:
| Script | Description | Risk Level |
|---|---|---|
| add_wordpress_admin.sql | WordPress admin account creation | ๐ด HIGH |
Purpose:
- Database manipulation
- WordPress security testing
- Privilege escalation testing
- Database access testing
Security Considerations:
โ ๏ธ WARNING: SQL Scripts for unauthorized database access
โข Creating admin accounts without authorization is ILLEGAL
โข Database manipulation without permission violates CFAA
โข Unauthorized privilege escalation is a federal crime
ONLY use on systems you own or have explicit written permission to test.
Location: /Scripts/YAML/
Purpose:
- Script configuration files
- Automation playbook definitions
- Tool settings and parameters
- Environment configurations
Do not run unreviewed or out-of-scope automation on client systems.
MANDATORY CHECKLIST:
โ Do I OWN the target system?
โ Do I have WRITTEN authorization to test?
โ Is the authorization CURRENT and VALID?
โ Does authorization SPECIFICALLY cover these scripts/techniques?
โ Have I verified the script won't cause harm?
โ Do I have rollback/recovery procedures?
โ Have I tested in an isolated environment first?
โ Am I prepared to document all activities?
โ Do I have emergency contacts ready?
โ Have I reviewed applicable laws and policies?
If you answered NO to ANY question: DO NOT RUN THE SCRIPT
Authorized Testing Workflow:
1. Authorization Phase:
โโ> Obtain written authorization
โโ> Verify scope includes script usage
โโ> Document authorization details
โโ> Prepare testing environment
โโ> Review scripts before execution
2. Preparation Phase:
โโ> Test scripts in isolated lab first
โโ> Understand exactly what each script does
โโ> Prepare monitoring and logging
โโ> Have rollback procedures ready
โโ> Coordinate with stakeholders
3. Execution Phase:
โโ> Follow authorized scope strictly
โโ> Document all commands and outputs
โโ> Monitor system impact continuously
โโ> Stop immediately if issues occur
โโ> Maintain communication with client
4. Post-Execution Phase:
โโ> Document findings thoroughly
โโ> Provide detailed activity logs
โโ> Recommend remediations
โโ> Secure/delete sensitive data
โโ> Archive documentation properly
Safe Learning Environments ONLY:
โ
AUTHORIZED Learning:
โข Personal virtual machines YOU created
โข Home lab equipment YOU own
โข University/school labs WITH permission
โข Authorized CTF platforms (HackTheBox, TryHackMe)
โข Bug bounty programs WITHIN scope
โข Dedicated training environments
๐ซ NEVER Test On:
โข School/work production systems
โข Your employer's network without written approval
โข Friends' or family members' systems
โข Public WiFi or networks
โข Cloud services without explicit permission
โข Any system you don't own or lack written authorization for
# EXAMPLE: Running in authorized test environment
# 1. Verify authorization
Get-Content authorization.txt
# 2. Set execution policy (if needed)
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
# 3. Run script with appropriate parameters
.\script.ps1 -Target "authorized-target.local" -Output "results.txt"
# 4. Document results
Get-Content results.txt | Out-File -FilePath "assessment-report.txt" -Append# EXAMPLE: Running network scanner in authorized environment
# 1. Verify you have authorization
# 2. Activate virtual environment (recommended)
python -m venv venv
source venv/bin/activate # Linux/Mac
venv\Scripts\activate # Windows
# 3. Install dependencies
pip install -r requirements.txt
# 4. Run script against authorized target only
python port_scanner.py --target 192.168.1.100 --output scan_results.txt
# 5. Document and secure results# EXAMPLE: Running reconnaissance script
# 1. Review script contents first
cat script.sh
# 2. Make executable
chmod +x script.sh
# 3. Run with proper parameters
./script.sh --target authorized-system.local --output results.txt
# 4. Review and document results
cat results.txtScripts range from local utilities to active access, scanning, credential, remote-control and data-handling tools. A category or risk label in this index is a triage aid, not a legal classification or guarantee that a command is safe.
For an engagement, record the approving authority, in-scope systems and accounts, allowed techniques, time window, data-handling limits, contacts, stop conditions and rollback plan. Confirm that the person granting permission can authorize the target and that the scope covers the specific method. Written approval is good practice; no single form is a universal legal requirement for every activity.
The CFAA statute (18 U.S.C. ยง 1030) contains several distinct offenses and penalty provisions. Application depends on statutory elements and facts. The DOJ charging policy is guidance for federal prosecutors, not a complete account of every federal, state, civil or international rule. Avoid relying on blanket claims such as โany unauthorized use is a federal crimeโ or one fixed prison term.
| Tool class | Main operational concern | Safer practice |
|---|---|---|
| Port scanners and discovery tools | Unexpected traffic, alerts or service load | Set a narrow approved target list, rate and time window; stop on instability |
| Login or password testing | Account lockouts, alerts and access to real accounts | Use test accounts in a lab or an explicitly scoped engagement; agree on attempt limits |
| Credential capture or data collection | Exposure of real secrets, personal or regulated data | Use synthetic test data; collect the minimum approved data and protect/delete it under the plan |
| Remote shells or system changes | Persistence, outages or unintended host changes | Use isolated labs or a documented change/rollback procedure on specifically approved systems |
| ICS/SCADA tools | Physical process and safety effects | Do not probe live control systems without owner authorization, engineering review and a safety-approved test plan |
An authorized test can still cause outages or expose data. Use the script execution workflow to review inputs, target scope, expected effects, monitoring, rollback and output handling before execution.
Before: validate the target and scope, inspect the script and dependencies, test in an isolated lab where feasible, prepare monitoring and rollback, and identify an escalation contact.
During: use the minimum required privileges and activity, record timestamps and commands, monitor service health, and stop if scope is unclear, a control blocks the activity, or unexpected impact appears.
After: report results, protect captured data, remove temporary access or test artifacts as agreed, verify recovery, and retain only the records required by the engagement.
Use intentionally vulnerable local VMs, CTF environments or systems specifically provided for training. Keep test networks isolated where practical, snapshot targets, and avoid connecting practice tools to unrelated or public systems.
We welcome contributions from security professionals, but all scripts must meet strict quality and ethical standards.
To Submit Scripts:
- Fork the repository
- Add scripts to appropriate language directory
- Include comprehensive documentation
- Add explicit legal warnings and usage requirements
- Test thoroughly in isolated environment
- Ensure code is clean, commented, and professional
- Submit pull request with detailed description
Script Quality Standards:
- โ Well-documented with clear comments
- โ Professional code quality and style
- โ Error handling and input validation
- โ Explicit authorization checks/warnings
- โ Logging and output formatting
- โ Usage instructions included
- โ Legal warnings prominent in code
- โ No hardcoded credentials or targets
โ Welcome Contributions:
- Security automation tools for authorized testing
- Defensive security scripts (detection, monitoring)
- Educational security demonstrations
- Vulnerability scanners with proper warnings
- Security analysis utilities
- Forensics and incident response tools
- CTF and training utilities
๐ซ Will NOT Accept:
- Malware or trojans
- Scripts designed solely for malicious use
- Exploits without educational/defensive value
- Tools targeting specific organizations
- Scripts with hardcoded targets
- Obfuscated malicious code
- Scripts violating any laws
Authorized Testing Environments:
- HackTheBox: https://www.hackthebox.com/
- TryHackMe: https://tryhackme.com/
- PentesterLab: https://pentesterlab.com/
- VulnHub: https://www.vulnhub.com/
- OverTheWire: https://overthewire.org/
- DVWA: Damn Vulnerable Web Application
- Metasploitable: Intentionally vulnerable VM
Understanding Computer Crime Laws:
- CFAA Text: 18 U.S.C. ยง 1030
- DOJ Computer Crime Manual: https://www.justice.gov/criminal-ccips
- EFF Cybersecurity: https://www.eff.org/
- SANS Acceptable Use Policy: https://www.sans.org/information-security-policy/
Certifications:
- OSCP: Offensive Security Certified Professional
- CEH: Certified Ethical Hacker
- GPEN: GIAC Penetration Tester
- GWAPT: GIAC Web Application Penetration Tester
- eWPT: eLearnSecurity Web Penetration Tester
Training Resources:
- Offensive Security: https://www.offsec.com/
- SANS Institute: https://www.sans.org/
- eLearnSecurity: https://ine.com/security
- Cybrary: https://www.cybrary.it/
- Pluralsight: Security training paths
- ๐ Main Repository
- ๐ฏ START HERE Guide
- ๐ป Cybersecurity Master Guide
- ๐ OSINT Resources
- โ Security Checklists
- ๐ Documentation
- ๐ OPSEC Guidelines
- ๐ PDF Library
- ๐ Playbooks
๐ Script Directories: 7 language categories
๐ป Languages: Bash, C, Go, PowerShell, Python, SQL, YAML
๐ง Script Count: 50+ security tools and utilities
โ ๏ธ Risk Level: HIGH - Offensive security tools
๐ Last Updated: November 2024
๐ฅ Maintained by: Pacific Northwest Computers (PNWC)
๐ Status: Active - Use with EXTREME CAUTION
1. AUTHORIZATION IS MANDATORY
โ Written authorization required
โ From person with authority to grant
โ Explicitly covers scripts and scope
โ Current and not expired
2. THESE ARE OFFENSIVE TOOLS
โ Designed for penetration testing
โ Can cause system damage
โ Capable of unauthorized access
โ Subject to strict legal regulations
3. LEGAL CONSEQUENCES ARE SEVERE
โ Federal imprisonment (up to 20 years)
โ Massive fines and restitution
โ Civil lawsuits and liability
โ Career-ending consequences
4. TEST SAFELY
โ Use isolated lab environments
โ Test on systems you own
โ Never test production without approval
โ Have rollback procedures ready
5. PROFESSIONAL STANDARDS
โ Document everything
โ Follow ethical guidelines
โ Report responsibly
โ Protect confidentiality
With great power comes great responsibility - and great legal liability.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
๐ด THESE ARE OFFENSIVE SECURITY TOOLS ๐ด
๐ด UNAUTHORIZED USE = FEDERAL CRIME ๐ด
๐ด UP TO 20 YEARS IMPRISONMENT ๐ด
๐ด WRITTEN AUTHORIZATION MANDATORY ๐ด
โญ Star this repo if you find it useful (and use it legally!) โญ
- ../README.md - Main repo index
- pnwc_install_tools.sh - Cross-distro tool installer (apt/pacman/dnf)
- Bash/bash_scripting_cheat-sheet.md - Bash scripting reference
- Bash/BashBunny/README.md - Bash Bunny payload setup & five authorized field assessment labs
- Ducky/README.md - USB Rubber Ducky compilation & six safe HID assessment exercises
- WiFi Pineapple Mark VII - complementary wireless Recon & WIDS exercises
- ../Documentation/blackarch.md - BlackArch tool installation context
pnwc_install_tools.sh keeps pip-managed libraries and commands in
/opt/pnwc-tools/venv, separate from the system interpreter. After installation,
activate it for a new shell or invoke its binaries by absolute path:
source /opt/pnwc-tools/venv/bin/activateOn Arch-family systems, complete sudo pacman -Syu before starting the installer.
The installer asks you to confirm that step and does not refresh package metadata
separately. An unattended run without confirmation stops before installing tools.
๐ Folder: Scripts | โ๏ธ Suggest an edit | ๐บ๏ธ Browse by Topic
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics