Twitter's own account caused blackout, says DNS provider
Twitter's authorized account made changes to DNS records, shunting users to hacker site, says Dyn Inc. — Computerworld - Hackers redirected Twitter.com's traffic to a rogue Web site for more than an hour early today by accessing …
Context & Ripple Effects
Twitter had spent late 2009 positioning itself as business infrastructure: the Contributors feature unveiled on December 16 was explicitly aimed at courting big business, and the service had already become the default back-channel at conferences. Two days later its front door failed — Dyn Inc., which manages Twitter.com's DNS, says attackers used Twitter's own authorized account to rewrite the records.
The attribution matters because it rules out a breach of Dyn itself. Computerworld's report, echoed in TechCrunch's anatomy of the attack and an official update on the Twitter blog, locates the compromise inside Twitter's account controls — and the breadth of same-day pickup is itself a measure of how load-bearing the service had become.
First-order effects
- Twitter.com traffic sat pointed at a rogue site for more than an hour until Dyn could restore correct records — the immediate damage lands on Twitter just as it pitches itself to enterprise customers.
- Dyn escapes direct blame: confirming the change came through an authorized customer account moves the security question off its own perimeter and onto Twitter's credential handling.
Second-order effects
- DNS providers and registrars serving high-profile domains face pressure to harden authentication around record changes — verification at the provider is cheaper than incident response at every customer.
- Brands evaluating Twitter's Contributors courtship must now weigh account-hijack risk in the channel itself; a service sold to businesses is only as credible as the protection around its own naming.
Third-order effects
- If one compromised login can blackhole a top-tier web property, DNS administration drifts toward critical-infrastructure practice: out-of-band confirmation, segregated admin accounts, audited changes.
- Accountability consolidates around whoever operates the name servers — providers inherit liability exposure when redirects occur, pushing the industry toward contractual security guarantees rather than best-effort uptime.
The trend: As entire platforms come to hinge on single DNS accounts, credential-level attacks against name servers displace brute-force failures as the dominant availability threat.