lookalike-domain
Register and provision a lookalike / Punycode phishing domain with DNS and TLS so GoPhish and evilginx2 lures resolve and pass modern mail + browser checks.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- lookalike-domain
- metadata
- { "tags": [ "phishing", "infrastructure", "domain", "dns" ], "subdomain": "phishing", "when_to_use": "lookalike domain, punycode, typosquat domain, idn homograph, phishing infrastructure, dns spf dkim dmarc, tls acme for lure", "mitre_attack": [ "T1583.001", "T1566", "T1656" ] }
- description
- Register and provision a lookalike / Punycode phishing domain with DNS and TLS so GoPhish and evilginx2 lures resolve and pass modern mail + browser checks.
03 SKILL.md 正文
Lookalike Domain
The lure link's domain must look plausible and pass SPF/DKIM/DMARC or
modern inboxes drop the mail and browsers flag the page. This skill
stands up the domain that gophish-campaign and evilginx2-proxy
sit behind.
Choose the name
- Combosquat / lookalike:
acme-portal.example,login-acme.example,acme-sso.example(a real word the victim associates with the brand). Prefer this over raw typos. - IDN homograph (Punycode): visually-similar Unicode characters
(
аcme.examplewith a Cyrillic а →xn--cme-8cd.example). Use only when the RoE allows and the mail path won't strip it.
python3 - <<'PY'
import idna
print(idna.encode("аcme.example").decode()) # punycode (xn--...)
PY
- NEVER pick a name confusable with a DIFFERENT customer's brand
(
plan/roe.jsonscope only).
DNS
A @ <sandbox-ip>
A login <sandbox-ip>
MX @ 10 mail.<lookalike>.
TXT @ "v=spf1 a mx ip4:<sandbox-ip> -all"
TXT default._domainkey "v=DKIM1; k=rsa; p=<pubkey>"
TXT _dmarc "v=DMARC1; p=none; rua=mailto:dmarc@<lookalike>"
For evilginx2, delegate NS to the sandbox so it can answer ACME challenges itself.
TLS
acme.sh --issue --standalone -d login.acme-portal.example
# or let evilginx2 manage Let's Encrypt automatically
Verify before sending
dig +short login.acme-portal.example
# check SPF/DKIM/DMARC alignment with a test send to a controlled box
swaks --to test@controlled.example --from it@acme-portal.example --server localhost
Evidence
Record the domain, registration date, and DNS records in
plan/phisher/infrastructure.md; this feeds the mandatory
lure-deconfliction handshake payload (the blue team needs the lure
domain + registration date). Create an Infrastructure node in the
knowledge graph.
Failsafe
On stop, dns_failover_to_safe: repoint the domain to a static
"authorized security test — contact your security team" page within 5
minutes.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.