Dead Infrastructure Hijacking (DIH) is the exploitation of residual trust relationships left when services, domains, or cloud storage are decommissioned, allowing an attacker who reclaims those endpoints to inherit trust and receive sensitive traffic without exploiting vulnerabilities. The report details three confirmed variants—SaaS CNAME subdomain takeover, expired domain registration, and cloud bucket squatting—corrects misconceptions about CAA and DNSSEC, and recommends organizational and technical mitigations including AWS Account Regional Namespaces and CT/historical DNS auditing. #AWSAccountRegionalNamespaces #CloudBucketSquatting
Keypoints
- Dead Infrastructure Hijacking (DIH) occurs when decommissioned endpoints (domains, CNAMEs, cloud buckets) remain trusted by live systems and are reclaimed by attackers to receive legitimate traffic without intrusion.
- Three confirmed DIH variants: CNAME-based subdomain takeover of unclaimed SaaS endpoints, expired domain registration, and cloud storage bucket squatting—each with distinct TLS constraints, exploitation modes, and impacts.
- Common DNS/TLS controls are frequently mischaracterized: CAA does not prevent SaaS CNAME takeover because platforms auto-provision certificates, and DNSSEC does not mitigate DIH because records legitimately point to attacker-controlled resources.
- AWS’s Account Regional Namespaces (launched March 12, 2026) removes S3 bucket squatting for new buckets by binding names to account+region, but does not retroactively protect existing buckets and requires opt-in enforcement.
- Remediation requires organizational change: explicit cross-functional decommissioning ownership, domain retention policies until downstream dependencies are cleared, CT and passive DNS historical discovery, and prioritized remediation of wildcard-covered subdomains.
- Detection and tooling sequence matters: run CT historical discovery before DNS audits, use PassiveTotal for historical DNS, and deploy dnsReaper, BadDNS, and Nuclei in sequence for comprehensive exposure identification.
MITRE Techniques
- [T1596.001 ] Search Open Technical Databases: DNS/Passive DNS – Used to obtain historical DNS resolution data to determine whether a lapsed webhook pointed to a SaaS CNAME or a custom domain (‘PassiveTotal’s passive DNS capability provides the historical resolution data needed for this determination.’)
- [T1593.002 ] Search Open Websites / Domains – Employed to discover historical subdomains and certificate issuance events through CT and other public records (‘Run CT log historical discovery (%.yourdomain.com) before any DNS audit tooling.’)
- [T1583.001 ] Acquire Infrastructure: Domains – Attackers register expired or lapsed domains that live systems still reference to inherit inbound traffic (‘The attacker registers a lapsed domain that live systems still reference.’)
- [T1584.006 ] Compromise Infrastructure: Web Services – Claiming unclaimed SaaS custom domain mappings or CDN distributions to serve malicious or cloned content under trusted subdomains (‘claiming the distribution through CloudFront’s standard account creation flow allowed arbitrary content to be served under the trusted subdomain’)
- [T1608.001 ] Stage Capabilities: Upload Malware – Re-registered cloud storage buckets are populated with malicious build artifacts or updates to poison supply chains (‘the re-registered buckets received traffic… Every one of those requests could have been answered with a malicious payload.’)
- [T1195.002 ] Supply Chain Compromise: Compromise Software Supply Chain – Bucket squatting in CI/CD pipelines enables active delivery of malicious artifacts to downstream systems and customer environments (‘a reclaimed S3 bucket in a CI/CD pipeline can deliver malicious build artifacts to every downstream system consuming that pipeline’)
- [T1566.003 ] Phishing: Spear phishing via Service – Elicitation mode includes serving login clones or redirects on hijacked subdomains to harvest credentials (‘The attacker serves a redirect to a login-page clone, an authentication error that prompts credential re-entry, or a session expiry notice soliciting re-authentication.’)
- [T1539 ] Steal Web Session Cookie – Cookie scope exploitation on parent-domain scoped session cookies allows stolen session identifiers to be sent to hijacked subdomains (‘If session cookies are scoped to the parent domain (domain=.example.com) rather than (domain=docs.example.com), a hijacked subdomain under that domain may receive those cookies’)
- [T1213 ] Data from Information Repositories – Passive collection mode captures telemetry, internal event records, and configuration data sent to lapsed endpoints (‘The value lies entirely in what arrives: authentication tokens… internal event records in webhook payloads, session identifiers in routine check-in calls, and diagnostic telemetry’)
- [T1567 ] Exfiltration Over Web Service – Reclaimed endpoints serve as receivers for sensitive tokens and telemetry exfiltrated by normal application traffic (‘a reclaimed endpoint and receives organic traffic has established a persistent collection point’)
- [T1036.005 ] Masquerading: Match Legitimate Name or Location – Attackers use legitimate-looking hostnames, wildcard certificates, or vendor-owned domains to make malicious endpoints indistinguishable from legitimate services (‘Browsers and applications trusting the wildcard connect without certificate errors means the wildcard is valid for all subdomains, including the one the attacker controls.’)
- [T1505.003 ] Server Software Component: Web Shell (analogy) – Active-mode payload delivery via hijacked storage or web endpoints can function analogously to server-side implants by delivering executable artifacts or configuration changes (‘the attacker delivers malicious content to systems, fetching build artifacts, software updates, or configuration files’)
Indicators of Compromise
- [Domain Name ] lapsed or re-registered domains referenced by live systems – api.old-service.com, example of expired custom domains used for telemetry or updates, and other recently re-registered domains observed in CT/passive DNS checks
- [Subdomain ] delegated CNAMEs pointing to unclaimed SaaS/CDN endpoints – docs.example.com, rider-facing subdomain (CloudFront CNAME) and 670 legacy Microsoft subdomains identified in external audits
- [Cloud Bucket Name ] S3/GCS/Azure storage names used to intercept pipeline artifacts – mybucket-123456789012-us-east-1-an (AWS Account Regional Namespace example), re-registered abandoned S3 bucket names, and ~150 re-created buckets observed in research
- [Artifact/File Types ] build and deployment artifacts requested from reclaimed storage – unsigned OS binaries, virtual machine images, JavaScript files, CloudFormation templates (examples of fetch types seen during two-month monitoring)
- [Certificate/CT Entry ] unexpected certificate transparency log entries for decommissioned subdomains – ‘%.yourdomain.com’ CT discoveries and unexpected certificate issuance for formerly decommissioned subdomains signaling possible takeover attempts