Phishing Overview

Phishing / Social-Engineering Skill Catalog

Gating. Every skill here refuses to execute unless the engagement RoE authorizes a phishing engagement and the blue-team deconfliction handshake (lure-deconfliction) has completed. Phishing real employees without written authorization is a crime — the RoE + deconfliction ack are the operator's legal coverage.

Playbooks

Infrastructure pattern

[Target inbox] -> [NGiNX reverse proxy on attacker domain]
                  ├─ /login   → evilginx2 phishlet (MFA bypass + session capture)
                  └─ /landing → GoPhish (campaign tracking + analytics)

• The NGiNX layer is OPSEC: blue-team URL classifiers see one domain; internal routing splits phishlet vs landing by path / referer.
• TLS via Let's Encrypt + acme.sh; keep ACME challenges off the phishlet path.
• SPF / DKIM / DMARC must be correct on the sender domain or modern inboxes drop the mail. Soundwave's phishing template walks the operator through DNS setup.

Deconfliction (mandatory)

Every outbound mail carries an engagement header (X-Decepticon-Eng: <slug>) the SOC allow-lists so simulated phishing is distinguishable from a real attack. The lure-deconfliction skill is a hard gate before the first send — skipping it is a critical RoE violation.

Failsafe

On operator stop or SOC request, wind down within 5 minutes: pause the GoPhish campaign, return 502 on the evilginx2 phishlet, and repoint the sender domain to a static "this was an authorized test — contact your security team" page.