The Hacker Mindset
Overview
Best Hacker channels elite offensive security methodology — finding vulnerabilities through creative exploitation, chaining weaknesses, and thinking like an adversary to strengthen systems.
Anti-Rationalization Table
| Rationalization |
Reality |
| "I'll figure it out as I go" |
A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" |
Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" |
The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" |
Adding complexity rarely solves process gaps. Master the core workflow first. |
When to Use
Trigger phrases:
- "best hacker"
- "Help me with best hacker"
Use cases:
- When the task matches this skill's domain expertise
Core Philosophy
"Security through obscurity is no security at all." — Hacker Creed
The Hacker Ethos:
- Curiosity - Always ask "what if?"
- Impatience - Don't wait for official channels
- Playfulness - See problems as puzzles
- Persistence - Try 1000 ways, not just 1
- Minimalism - Simplest path to goal
Attack Methodology
Structured approach: recon, enumeration, exploitation, post-exploitation.
1. Reconnaissance
"To beat the system, know the system."
Information Gathering:
- OSINT (Open Source Intelligence)
- Social media profiling
- Company org charts
- Technology stack discovery
- Employee information
Tools:
- LinkedIn, Facebook, Twitter
- Company websites, press releases
- Job postings (reveals tech stack)
- Shodan, Censys for infrastructure
2. Vulnerability Identification
The Attack Surface:
Entry Points:
├── Web apps (port 80, 443)
├── Email (port 25, 587)
├── VPN (port 443, 1194)
├── Cloud services
├── Mobile apps
└── Social engineering
Vulnerability Classes:
- Technical: SQL injection, XSS, buffer overflow
- Config: default passwords, exposed files
- Human: phishing, social engineering
- Physical: badge cloning, tailgating
3. Exploitation
The Exploit Chain:
- Find weakness → Gain access → Escalate → Maintain → Exfiltrate
Common Exploits:
- Credential stuffing
- Privilege escalation
- Buffer overflow
- DLL hijacking
- Session hijacking
Defense Through Offense
Understanding attack patterns to build better defenses.
Think Like Attacker:
What would I do if I wanted to:
├── Steal this data?
├── Take this system down?
├── Access this network?
└── Impersonate this user?
Security Checklist:
The 3 Defense Layers:
- Perimeter - Firewall, WAF, VPN
- Internal - Network segmentation, IAM
- Endpoint - EDR, antivirus, encryption
Red Team Framework
Rules of engagement, scope boundaries, and reporting standards.
Assessment Process:
- Planning: Define scope, goals, rules
- Recon: Gather intelligence
- Scanning: Find vulnerabilities
- Exploitation: Test attacks
- Documentation: Report findings
Purple Team (Offense + Defense):
- Both teams work together
- Real-time learning
- Continuous improvement
When NOT to Use
- When the research requires access to proprietary databases or paywalled sources
- When findings will be used for financial decisions requiring licensed advisor review
- When the task is too trivial to warrant this skill
- When a more appropriate skill exists
Common Rationalizations
| Rationalization |
Reality |
| "I'll do this later" |
Explain why this excuse is wrong for this skill |
| "This is simple, skip steps" |
Even simple tasks benefit from process |
Red Flags
- Research relies on a single unverified source
- Agent presents speculation as confirmed findings
- Watch for shortcuts and skipped steps
Workflow
- Understand requirements — Clarify objectives and scope
- Set up tools — Configure required tools and access
- Execute — Perform the core operations
- Validate — Verify results meet quality standards
- Document — Record findings and decisions
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
After completing this skill, confirm:
Related Skills
systematic-debugging - Finding problemssecurity-reviewer - Security analysiscode-reviewer - Finding code vulnerabilitiesverification-before-completion - Testing
1---2name: best-hacker3description: Use when apply hacker mindset to find vulnerabilities, break assumptions, and stress-test systems before attackers do. Use when working with best hacker.4license: Apache-2.05---67# The Hacker Mindset89## Overview1011**Best Hacker** channels elite offensive security methodology — finding vulnerabilities through creative exploitation, chaining weaknesses, and thinking like an adversary to strengthen systems.12131415## Anti-Rationalization Table1617| Rationalization | Reality |18|---|---|19| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |20| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |21| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |22| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |2324## When to Use2526**Trigger phrases:**27- "best hacker"28- "Help me with best hacker"2930**Use cases:**31- When the task matches this skill's domain expertise3233---3435## Core Philosophy3637> "Security through obscurity is no security at all." — Hacker Creed3839### The Hacker Ethos:40411. **Curiosity** - Always ask "what if?"422. **Impatience** - Don't wait for official channels433. **Playfulness** - See problems as puzzles444. **Persistence** - Try 1000 ways, not just 1455. **Minimalism** - Simplest path to goal4647## Attack Methodology4849Structured approach: recon, enumeration, exploitation, post-exploitation.505152### 1. Reconnaissance5354> "To beat the system, know the system."5556**Information Gathering:**57- OSINT (Open Source Intelligence)58- Social media profiling59- Company org charts60- Technology stack discovery61- Employee information6263**Tools:**64- LinkedIn, Facebook, Twitter65- Company websites, press releases66- Job postings (reveals tech stack)67- Shodan, Censys for infrastructure6869### 2. Vulnerability Identification7071**The Attack Surface:**72```73Entry Points:74├── Web apps (port 80, 443)75├── Email (port 25, 587)76├── VPN (port 443, 1194)77├── Cloud services78├── Mobile apps79└── Social engineering80```8182**Vulnerability Classes:**83- Technical: SQL injection, XSS, buffer overflow84- Config: default passwords, exposed files85- Human: phishing, social engineering86- Physical: badge cloning, tailgating8788### 3. Exploitation8990**The Exploit Chain:**911. Find weakness → Gain access → Escalate → Maintain → Exfiltrate9293**Common Exploits:**94- Credential stuffing95- Privilege escalation96- Buffer overflow97- DLL hijacking98- Session hijacking99100## Defense Through Offense101102Understanding attack patterns to build better defenses.103104105### Think Like Attacker:106107```108What would I do if I wanted to:109├── Steal this data?110├── Take this system down?111├── Access this network?112└── Impersonate this user?113```114115### Security Checklist:116117- [ ] Multi-factor authentication everywhere118- [ ] Least privilege access119- [ ] Network segmentation120- [ ] Regular penetration testing121- [ ] Employee security training122- [ ] Incident response plan123- [ ] Logging and monitoring124- [ ] Regular patches/updates125126### The 3 Defense Layers:1271281. **Perimeter** - Firewall, WAF, VPN1292. **Internal** - Network segmentation, IAM1303. **Endpoint** - EDR, antivirus, encryption131132## Red Team Framework133134Rules of engagement, scope boundaries, and reporting standards.135136137### Assessment Process:1381391. **Planning**: Define scope, goals, rules1402. **Recon**: Gather intelligence1413. **Scanning**: Find vulnerabilities1424. **Exploitation**: Test attacks1435. **Documentation**: Report findings144145### Purple Team (Offense + Defense):146147- Both teams work together148- Real-time learning149- Continuous improvement150151---152153154## When NOT to Use155156- When the research requires access to proprietary databases or paywalled sources157- When findings will be used for financial decisions requiring licensed advisor review158- When the task is too trivial to warrant this skill159- When a more appropriate skill exists160161## Common Rationalizations162163| Rationalization | Reality |164|---|---|165| "I'll do this later" | Explain why this excuse is wrong for this skill |166| "This is simple, skip steps" | Even simple tasks benefit from process |167168## Red Flags169170- Research relies on a single unverified source171- Agent presents speculation as confirmed findings172- Watch for shortcuts and skipped steps173174175## Workflow1761771. **Understand requirements** — Clarify objectives and scope1782. **Set up tools** — Configure required tools and access1793. **Execute** — Perform the core operations1804. **Validate** — Verify results meet quality standards1815. **Document** — Record findings and decisions182183184## Process1851861. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1871. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1881. **Reporting** — Document IOCs, write findings, provide remediation recommendations189190## Verification191192After completing this skill, confirm:193194- [ ] Findings are verified across multiple independent sources195- [ ] Research methodology is documented and reproducible196- [ ] All required outputs generated197- [ ] Success criteria met198199## Related Skills200201- `systematic-debugging` - Finding problems202- `security-reviewer` - Security analysis203- `code-reviewer` - Finding code vulnerabilities204- `verification-before-completion` - Testing
oyi77