How I Built It

GoPhish Setup

I used GoPhish as the phishing platform β€” it handles email templates, campaign management, and tracking all in one place. Here's what I set up:

  • Configured SMTP for email delivery to my own inbox
  • Built HTML email templates using GoPhish's variable injection ({{.URL}}, {{.FirstName}}) to make them feel personalized
  • Created a fake login page to demonstrate how credential harvesting works
  • Used GoPhish's built-in dashboard to track opens, clicks, and form submissions

🎣 The Phishing Attack Lifecycle

A humorous look at how phishing attacks typically progress (educational purposes only!)

πŸ“§

1. Malicious Link

"Click here to claim your prize!"

β†’
🎣

2. Credential Harvest

"Please verify your account..."

β†’
πŸšͺ

3. Initial Access

Attacker logs into account

🦠

4. Malware Delivery

Trojan/Keylogger installed

β†’
πŸ•ΈοΈ

5. Lateral Movement

Spreads to other systems

β†’
πŸ’Ύ

6. Data Exfiltration

Sensitive data stolen

β†’
πŸ›‘οΈ

Prevention: Security Awareness!

The best defense is education + MFA + email filtering

πŸŽ“ What I Learned

Why Social Engineering Works

The biggest takeaway from this project: phishing doesn't exploit software vulnerabilities β€” it exploits how people think. Even knowing it was my own test campaign, the emails I crafted looked convincing. That's what makes social engineering so dangerous.

  • Authority: People trust emails that look like they come from IT, HR, or a boss. I tested templates impersonating all three β€” they all looked real
  • Urgency: Adding a fake deadline ("Your account will be locked in 24 hours") makes people act before they think
  • Familiarity: Clean formatting and familiar branding bypasses the gut check. A sloppy email gets ignored; a polished one gets clicked
  • Context: Timing matters β€” a "password reset" email right after a company announces a system migration would catch people off guard

Red Flags Users Should Spot

Building these emails myself taught me exactly what to look for when I'm on the receiving end:

  • Generic greetings like "Dear User" instead of your actual name
  • Urgency or threats designed to make you panic ("Account suspended", "Immediate action required")
  • Sender address doesn't match the display name β€” always check the actual email header
  • Unexpected requests for credentials or personal info (legitimate services rarely ask for this via email)
  • Hover over links before clicking β€” the URL in the text and the actual destination are often completely different

πŸ›‘οΈ Defensive Recommendations

πŸ”
Enable MFA

Even if phished, MFA prevents access

πŸ“§
Email Filtering

SPF, DKIM, DMARC, link scanning

πŸŽ“
User Training

Regular simulations & education

🚨
Report Button

Easy reporting mechanisms