Map a phishing campaign from a single hijacked subdomain

A Tetrisponse investigator gave an AI agent one dead subdomain from a client breach; it mapped dozens of hijacked domains, but also falsely listed five innocent companies as victims.

Done withCustom agent· Nov 4, 2026

What they did

After a client's employee signed in on a fake login page reached through a paid search ad, Reut Menashe of the security firm Tetrisponse ran most of the follow-up investigation through an AI agent. The agent got one dead subdomain and was asked to find the rest of the operation. It worked across certificate transparency logs, passive DNS, scan archives and domain registration records, cross-referencing them and building a timeline. The firm did not name the agent or model it used.

How it went

The agent turned one incident into a whole campaign: dozens of hijacked business domains, a shared cloaking page that kept the malicious ads past review, and a backend collecting Google logins. It spotted that the operator had put several victims on one TLS certificate and used that to find more, and it split the attacker's own throwaway domains from the hijacked ones. The firm reported the backend and a registrar took it down, but it came back on new domains within the week. The victim list also named five Israeli companies that were never compromised: they only shared Cloudflare IP addresses with attacker sites, and the agent wrote them up with the same confidence as the real finds.

Worth knowing

Shared IPs behind a CDN are a weak link, and the agent treated them as proof. The team only counts a domain as a victim when a live host on it resolves to the attacker's server at the time of writing. This is a security firm's own write-up of its work, with the client unnamed and no indicators published.

Try it

With Custom agent· 2 parts to fill in

Investigate the infrastructure behind [suspicious domain or subdomain]. Use [certificate transparency logs, passive DNS, scan archives, WHOIS or the sources I have access to] to find related domains, shared certificates and hosting. Separate domains the attacker registered from legitimate domains that look hijacked. For every domain you list as a victim, give the evidence and mark it verified only if a live host on it resolves to attacker infrastructure right now; a shared IP or CDN address alone is not enough. Do not contact anyone or report anything. Stop and give me the map with a confidence level on each claim.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related