| name | building-adversary-infrastructure-tracking-system |
| description | Build an automated system to track adversary infrastructure using passive DNS, certificate transparency, WHOIS data, and IP enrichment to map and monitor threat actor command-and-control networks. |
| domain | cybersecurity |
| subdomain | threat-intelligence |
| tags | ["infrastructure-tracking","passive-dns","c2","whois","threat-actor","pivoting","threat-intelligence","domain-analysis"] |
| version | 1.0 |
| author | mahipal |
| license | Apache-2.0 |
Building Adversary Infrastructure Tracking System
Overview
Adversary infrastructure tracking uses passive DNS records, certificate transparency logs, WHOIS registration data, and IP enrichment to discover, map, and monitor threat actor command-and-control (C2) networks. Attackers frequently reuse hosting providers, registrars, SSL certificates, and naming patterns across campaigns, enabling analysts to pivot from known indicators to discover new infrastructure. This skill covers building an automated tracking system that identifies infrastructure relationships, detects newly registered domains matching adversary patterns, and maintains a continuously updated map of threat actor networks.
Prerequisites
- Python 3.9+ with
requests, dnspython, python-whois, shodan, networkx libraries
- API keys: SecurityTrails, PassiveTotal/RiskIQ, Shodan, VirusTotal
- Access to passive DNS data sources
- Understanding of DNS infrastructure, hosting, and domain registration
- Graph database (Neo4j) or NetworkX for relationship visualization
Key Concepts
Passive DNS
Passive DNS captures historical DNS resolution data, recording which domains resolved to which IPs and when. Unlike active DNS queries, passive DNS preserves historical relationships even after records change, enabling analysts to track infrastructure changes, identify shared hosting patterns, and discover related domains that resolved to the same IP addresses over time.
Infrastructure Pivoting
Pivoting identifies related infrastructure by following connections: IP pivot (find all domains on an IP), domain pivot (find all IPs a domain resolved to), WHOIS pivot (find domains with same registrant), certificate pivot (find hosts sharing SSL certificates), and NS/MX pivot (find domains using same name servers or mail servers).
Adversary Infrastructure Patterns
Threat actors exhibit patterns: preferred registrars (Namecheap, REG.RU, Tucows), preferred hosting (bulletproof hosting providers, cloud services), domain generation algorithms (DGA), consistent naming patterns, and certificate reuse across campaigns.
Practical Steps
Step 1: Passive DNS Infrastructure Discovery
import requests
import json
from collections import defaultdict
from datetime import datetime
class InfrastructureTracker:
def __init__(self, securitytrails_key=None, vt_key=None, shodan_key=None):
self.st_key = securitytrails_key
self.vt_key = vt_key
self.shodan_key = shodan_key
self.infrastructure_graph = defaultdict(lambda: {"nodes": set(), "edges": []})
def passive_dns_lookup(self, domain):
"""Query passive DNS for domain resolution history."""
headers = {"apikey": self.st_key}
url = f"https://api.securitytrails.com/v1/history/{domain}/dns/a"
resp = requests.get(url, headers=headers, timeout=30)
if resp.status_code == 200:
records = resp.json().get("records", [])
history = []
for record in records:
for value in record.get("values", []):
history.append({
"domain": domain,
"ip": value.get("ip", ""),
: record.get(, ),
: record.get(, ),
: record.get(, ),
})
()
history
[]
():
headers = {: .st_key}
url =
resp = requests.get(url, headers=headers, timeout=)
resp.status_code == :
blocks = resp.json().get(, [])
domains = []
block blocks:
site block.get(, []):
domains.append(site)
()
domains
[]
():
headers = {: .st_key}
url =
resp = requests.get(url, headers=headers, timeout=)
resp.status_code == :
data = resp.json()
whois_data = {
: domain,
: data.get(, ),
: data.get(, ),
: data.get(, ),
: data.get(, []),
: data.get(, ),
: data.get(, ),
: data.get(, ),
}
whois_data
{}
():
discovered = {: (), : (), : []}
indicator_type == :
discovered[].add(seed_indicator)
pdns = .passive_dns_lookup(seed_indicator)
record pdns:
ip = record[]
discovered[].add(ip)
discovered[].append({
: seed_indicator, : ip,
: ,
: record[],
: record[],
})
depth > :
reverse_domains = .reverse_ip_lookup(ip)
rd reverse_domains[:]:
discovered[].add(rd)
discovered[].append({
: rd, : ip,
: ,
})
indicator_type == :
discovered[].add(seed_indicator)
domains = .reverse_ip_lookup(seed_indicator)
domain domains[:]:
discovered[].add(domain)
discovered[].append({
: domain, : seed_indicator,
: ,
})
(
)
discovered
tracker = InfrastructureTracker(
securitytrails_key=,
vt_key=,
)
Step 2: Build Infrastructure Graph
import networkx as nx
class InfrastructureGraph:
def __init__(self):
self.graph = nx.Graph()
def add_discovery(self, discovery_data):
"""Add discovered infrastructure to graph."""
for domain in discovery_data["domains"]:
self.graph.add_node(domain, type="domain")
for ip in discovery_data["ips"]:
self.graph.add_node(ip, type="ip")
for rel in discovery_data["relationships"]:
self.graph.add_edge(
rel["source"], rel["target"],
relationship=rel["type"],
first_seen=rel.get("first_seen", ""),
last_seen=rel.get("last_seen", ""),
)
def find_clusters(self):
"""Identify infrastructure clusters."""
components = list(nx.connected_components(self.graph))
clusters = []
for component in components:
domains = [n for n in component .graph.nodes[n].get() == ]
ips = [n n component .graph.nodes[n].get() == ]
clusters.append({
: (component),
: (domains),
: (ips),
: (domains),
: (ips),
})
clusters.sort(key= x: x[], reverse=)
()
clusters
():
centrality = nx.degree_centrality(.graph)
top_nodes = (centrality.items(), key= x: x[], reverse=)[:top_n]
hubs = []
node, score top_nodes:
hubs.append({
: node,
: .graph.nodes[node].get(, ),
: (score, ),
: .graph.degree(node),
})
hubs
():
data = nx.node_link_data(.graph)
(output_file, ) f:
json.dump(data, f, indent=)
(
)
infra_graph = InfrastructureGraph()
discovery = tracker.pivot_from_seed(, depth=)
infra_graph.add_discovery(discovery)
clusters = infra_graph.find_clusters()
hubs = infra_graph.find_hub_nodes()
infra_graph.export_graph()
Step 3: Monitor for New Infrastructure
import time
class InfrastructureMonitor:
def __init__(self, tracker, known_indicators):
self.tracker = tracker
self.known = set(known_indicators)
self.alerts = []
def check_new_registrations(self, patterns):
"""Check for newly registered domains matching adversary patterns."""
import re
new_domains = []
for pattern in patterns:
headers = {"apikey": self.tracker.st_key}
url = "https://api.securitytrails.com/v1/domains/list"
params = {"include_ips": "true", "page": 1}
body = {"filter": {"keyword": pattern}}
resp = requests.post(url, headers=headers, json=body, timeout=30)
if resp.status_code == 200:
records = resp.json().get("records", [])
for record in records:
domain = record.get("hostname", "")
if domain not in self.known:
new_domains.append({
"domain": domain,
"pattern_matched": pattern,
: datetime.now().isoformat(),
})
.known.add(domain)
new_domains:
()
.alerts.extend(new_domains)
new_domains
():
report =
hub hubs[:]:
report += (
)
report +=
i, cluster (clusters[:], ):
report +=
report +=
report +=
(, ) f:
f.write(report)
()
monitor = InfrastructureMonitor(tracker, known_indicators=())
Validation Criteria
- Passive DNS queries return historical resolution data
- Reverse IP lookups discover co-hosted domains
- Infrastructure pivoting expands from seed indicators
- Graph analysis identifies clusters and hub nodes
- New infrastructure detected through pattern monitoring
- Reports generated with actionable recommendations
References
