/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Researchers: October's Mirai botnet attack on Dyn DNS service was incidental; original target was PlayStation Network name servers used by Dyn

Russell Brandom / The Verge :

The Verge Russell Brandom

Context & Ripple Effects

When the October 2016 outage hit, researchers traced it to a Mirai-based botnet built from DVRs and cameras with XiongMai components and framed Dyn itself as the target. This new finding rewrites that framing: Dyn was the delivery point, not the destination — the attackers were aiming at the PlayStation Network name servers Dyn happened to host.

That matters because Mirai has kept proving itself as reusable infrastructure since then, from the attempt to DDoS the domain hardcoded into WannaCry's kill-switch to researchers' later cost accounting of the 77-hour KrebsOnSecurity attack. Reattributing the Dyn strike from 'attack on DNS' to 'attack on a gaming network reached through DNS' changes who the adversary was and what they wanted.

First-order effects

  • Sony's PlayStation Network moves from bystander to named intended target of the October attack, while Dyn's role is recast as collateral host of the PSN name servers.

Second-order effects

  • DNS and other shared-infrastructure providers now inherit their customers' adversaries: anyone hosting high-profile name servers faces attacks aimed at those clients, not just at themselves.

Third-order effects

  • If the pattern holds, attribution and defense shift from protecting individual services to treating rented IoT botnet capacity as ambient threat — meaning every service sharing infrastructure with a popular target carries someone else's risk.

The trend: Insecure IoT botnets are turning shared internet infrastructure into collateral-damage territory, letting attackers reach one service by striking the provider both depend on.