Skip to content

Scripts

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

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.

๐Ÿ’ป Security Scripts & Tools

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

Bash PowerShell Python C


External script sourcing: Curated security GitHub collections describe useful upstream projects; no linked payload is automatically vetted or installed.

๐Ÿ“‹ Table Of Contents


๐ŸŽฏ Purpose

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.

โš™๏ธ Function

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.

๐Ÿ† Goal

A reader can find the right script for a task by category/language and understands the legal authorization requirement before running anything.

๐Ÿ“‹ When To Use

When looking for an existing script before writing a new one, or when unsure what legal/usage constraints apply to this folder's contents.

๐ŸŽฏ Overview

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.

โš ๏ธ Use and Scope

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.


๐Ÿ“‚ Directory Structure

Programming Language Categories

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

๐Ÿ—‚๏ธ Script Categories

1. Bash Scripts

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)

2. C Programs

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.

3. Powershell Scripts

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.

4. Python Scripts

Location: /Scripts/Python/

Current Scripts:

Network & Reconnaissance

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

Credential & Authentication

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

Bluetooth & Wireless

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

Exploitation & Attack Tools

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

Web & Application Security

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

Geolocation & Tracking

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

Mobile Device

Script Description Risk Level
iphone_finder.py iPhone device discovery ๐ŸŸก MEDIUM
iphone_messages.py iPhone message extraction ๐Ÿ”ด HIGH

Specialized Tools

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

Supporting Files

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

5. SQL Scripts

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.

6. YAML Configuration Files

Location: /Scripts/YAML/

Purpose:

  • Script configuration files
  • Automation playbook definitions
  • Tool settings and parameters
  • Environment configurations

๐Ÿ“– How To Use These Scripts

Authorized script review execution and rollback workflow

Do not run unreviewed or out-of-scope automation on client systems.

โš ๏ธ Before Running Any Script

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

For Security Professionals

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

For Students & Learners

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

Script Usage Guidelines

Powershell Scripts

# 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

Python Scripts

# 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

Bash Scripts

# 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.txt

โš ๏ธ Security, Authorization & Operational Risk

Scripts 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.

Establish scope before active testing

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.

Match precautions to the tool

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.

Practical checklist

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.

Isolated practice

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.

๐Ÿค Contributing

Contributing Scripts

We welcome contributions from security professionals, but all scripts must meet strict quality and ethical standards.

Contribution Guidelines

To Submit Scripts:

  1. Fork the repository
  2. Add scripts to appropriate language directory
  3. Include comprehensive documentation
  4. Add explicit legal warnings and usage requirements
  5. Test thoroughly in isolated environment
  6. Ensure code is clean, commented, and professional
  7. 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

What We Accept

โœ… 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

๐Ÿ“š Resources

Safe Learning Platforms

Authorized Testing Environments:

Legal Resources

Understanding Computer Crime Laws:

Professional Development

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:


๐Ÿ”— Quick Links

Internal Links

External Resources


๐Ÿ“Š Repository Statistics

๐Ÿ“ 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

๐ŸŽ“ Critical Reminders

Always Remember

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

โš ๏ธ USE THESE SCRIPTS RESPONSIBLY AND LEGALLY โš ๏ธ

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!) โญ

Related Files

Python Environment Used By The Tool Installer

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/activate

On 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.


๐Ÿ“‘ All Pages in Scripts

Guides & Reference

Bash

Bash / Bash Bunny

Ducky

GO

GO / shells


๐Ÿ“‚ Folder: Scripts | โœ๏ธ Suggest an edit | ๐Ÿ—บ๏ธ Browse by Topic

Clone this wiki locally