Skip to main content

Overview

Phishing is often necessary when traditional vulnerability exploitation fails. This methodology covers the full lifecycle of a phishing campaign from reconnaissance through credential capture.

Campaign Lifecycle

1

Recon the Victim

  • Select the victim domain.
  • Find login portals to impersonate via web enumeration.
  • Use OSINT to discover email addresses.
2

Prepare the Environment

  • Buy a phishing domain (similar to the victim’s).
  • Configure email authentication records: SPF, DMARC, DKIM, rDNS.
  • Set up a VPS with GoPhish.
3

Prepare the Campaign

  • Create a convincing email template.
  • Build or clone a credential-harvesting web page.
4

Launch

Import targets, configure the sending profile, and launch the campaign.

Domain Selection Techniques

Typosquatting Methods

Tools: dnstwist, urlcrazy, dnstwist.it

Buying Trusted Domains

Search expireddomains.net for expired domains with established reputation. Verify category with:

Email Infrastructure Setup

DNS Records Required

DKIM Configuration

Configure DKIM with Postfix and concatenate the B64 key values:

Test Your Configuration

Expected output:

GoPhish Configuration

Installation

TLS Certificate

GoPhish config.json

MFA Bypass Techniques

MitM Proxy (evilginx2 / muraena)

These tools act as a transparent proxy between the victim and the real site, capturing sessions including MFA tokens:
  1. Victim visits your phishing page.
  2. Tool proxies requests to the real site and checks credentials.
  3. If MFA is requested, the fake page relays it to the real site.
  4. Once authenticated, you capture credentials, MFA tokens, and session cookies.

VNC Session Phishing

Instead of a fake page, send the victim a VNC session connected to the real website — capturing everything they do.

MFA Fatigue / Help-Desk Reset

Modern intrusion sets bypass MFA entirely by targeting the help desk:
1

Recon

Harvest personal details from LinkedIn, data breaches, and public GitHub. Identify the exact help-desk MFA reset process.
2

Social Engineering

Phone or chat the help desk impersonating the target (with spoofed caller-ID or cloned voice). Provide collected PII to pass knowledge-based verification. Request MFA secret reset or SIM-swap.
3

Post-Access (within 60 min)

Enumerate AD/AzureAD with built-in tools, then move laterally:

AI-Enhanced Phishing

LLM-Assisted Runtime JavaScript Stealers

Attackers can ship benign-looking HTML and generate malicious JavaScript at runtime by querying a trusted LLM API:
This technique produces unique stealers per session with no static payload — standard static analysis will miss it. Run sandboxes with JavaScript enabled and flag eval() calls sourced from LLM API responses.

Clipboard Hijacking (Pastejacking)

Attackers silently overwrite the clipboard with malicious commands from a compromised web page, then trick users into pasting them into Win+R or a terminal.

Mobile Phishing

  • QR social engineering — Fake CERT/ministry pages display a WhatsApp Web QR, silently linking the attacker as a device.
  • APK distribution — Malicious Android apps embed spyware, exfiltrating contacts, documents, and device IDs.
  • Mobile-gated phishing — Operators detect mobile browsers and serve the phishing page only to mobile users, evading desktop crawlers.

References