Skip to content
View Gerrrt's full-sized avatar
⌨️
How does one code?
⌨️
How does one code?

Block or report Gerrrt

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Gerrrt/README.md

Gerrrt 👋

$ whoami
army cyber warrant officer · red teamer · writes crappy tools · breaks things... unintentionally

I'm a U.S. Army cyber warrant officer (CW2 / 170A) and I've spent about 14 years trying to figure out computers. These days that's mostly red teaming, pentesting, and writing throwaway Python/Bash that makes the tedious 80% go faster. Lately I've been trying to figure out threat hunting.


🎯 Experience

Discipline What that looks like
🔴 Red Teaming Full-scope engagements, TTPs, defensive evasion, post-exploitation tradecraft.
🧩 Penetration Testing Network, AD, and application testing.
⚙️ Ethical Hacking & Weaponization Python and Bash enumeration tooling, exploitation, and reporting.
🔵 Threat Hunting (actively expanding) Turning offensive knowledge inward and building detections.

🧬 Skills

Languages I live in: Python · Bash · PowerShell · a little C · Linux everything.

ATT&CK Tactic Tooling & techniques I operate
Recon & Resource Dev Nmap · OSINT · infrastructure & redirectors
Initial Access Phishing tradecraft · Exploitation · Burp Suite
Execution & Persistence Custom Python/Bash tooling · LOLBINS
Privilege Escalation BloodHound · Impacket · Active Directory
Defense Evasion Payload development · obfuscation · tradecraft
Credential Access & Lateral Movement Impacket · Kerberos · pivoting
Command & Control Metasploit · C2 profile & infrastructure design
Detection (blue-side) Splunk · ELK · Detection Engineering

Everything I publish is sanitized, and built to be understood by blue and red teams.


🎖️ Certs

OSCP — May 2019


🗺️ Current Projects

Repo What it is
👾 dotgibson My whole dotfiles ecosystem — one authored-once core (zsh · nvim · tmux) vendored across macOS, Windows/WSL2 & five Linux distros, with 🔴 offensive and 🔵 defensive role layers bolted on
🧠 htpx ATT&CK-tagged, red↔blue-paired methodology corpus — every technique beside its detection
🧪 ezekiellabs Red/blue/purple team tooling — one tool so far: opseclint

Inside dotgibson: core · Kali 🔴 · Defense 🔵 · web · plus per-OS repos for macOS · Windows · Arch · Fedora · openSUSE · Gentoo · Alpine.


📊 GitHub Metrics

GitHub metrics

📡 Reach Me

Email LinkedIn

Pinned Loading

  1. dotgibson/dotfiles-core dotgibson/dotfiles-core Public

    🧬 The shared Core of a cross-platform dotfiles system — zsh · nvim · tmux · starship, authored once and vendored into every OS. Zero drift.

    Shell

  2. dotgibson/dotfiles-MacBook dotgibson/dotfiles-MacBook Public

    🍎 The macOS layer — Homebrew, AeroSpace tiling, sketchybar & karabiner, over a shared zsh/nvim/tmux core. Keyboard-driven, drift-free.

    Shell

  3. dotgibson/dotfiles-Windows dotgibson/dotfiles-Windows Public

    🪟 The Windows host layer — PowerShell, Windows Terminal, scoop/winget, psmux (native tmux) & the WSL2 bridge. A first-class CLI on Windows.

    PowerShell 1

  4. dotgibson/dotfiles-Kali dotgibson/dotfiles-Kali Public

    🔴 The offensive role layer — recon→exploit→evasion field refs (hacktheplanet/exploitdev) on a Kali/WSL2 base. Engagement-ready.

    Shell

  5. dotgibson/dotfiles-web dotgibson/dotfiles-web Public

    🌐 The public showcase & docs for a cross-platform dotfiles system. Built with Astro, themed Tokyo Night, shipped on GitHub Pages.

    Astro