/
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
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

NSA uses FOXACID system to select and serve exploits to predetermined targets

The NSA's New Risk Analysis  —  As I recently reported in the Guardian, the NSA has secret servers on the Internet that hack into other computers, codename FOXACID.  These servers provide an excellent demonstration …

Schneier on Security Bruce Schneier

Context & Ripple Effects

Bruce Schneier's Guardian report on FOXACID lands mid-way through the 2013 Snowden disclosures, and it fills in the delivery half of a picture the summer's leaks had only sketched. By early September 2013, confirmed reporting showed the NSA working to undermine privacy-protecting encryption through court orders and technical pressure; by late August, documents had shown it cracked the UN's internal videoconferencing system. FOXACID explains how exploits actually reach the machines behind those capabilities.

The pickup pattern matters as much as the substance: the same day, Ars Technica, SiliconANGLE and the Guardian all carried the story, making FOXACID one of the more widely syndicated single-system reveals of the leak stream rather than a niche spycraft footnote.

First-order effects

  • Predetermined targets whose browsing reaches an NSA-controlled server face automated exploit delivery selected for their specific machine — the targeting decision is decoupled from the hacking act, letting the agency scale intrusions like a web service.
  • Security researchers and vendors now have a named, documented attack infrastructure to analyze, shifting the defensive conversation from generic malware attribution to the mechanics of state-run drive-by exploitation.

Second-order effects

  • Browser, plugin and operating-system makers face direct pressure to shrink the exploit surface these servers rely on, accelerating the hardening work that followed the NSA's documented war on encryption reported in September 2013.
  • Foreign governments and enterprises that absorbed the earlier revelations about raw intelligence sharing with Israel and financial spying now have concrete evidence that ordinary internet use is an attack vector, feeding procurement debates over US-built software and hardware.

Third-order effects

  • FOXACID models offensive cyber operations as reusable platforms — target selection, exploit serving, and payload delivery as separate layers — a structure that lowers the marginal cost of each new intrusion and invites imitation by other states and commercial surveillance vendors.
  • The system crystallizes the policy tension between stockpiling exploitable vulnerabilities for intelligence gain and disclosing them for collective defense; if hoarding remains the default, every hardened target list doubles as an unpatched risk shared with the entire internet.

The trend: State hacking is industrializing into layered delivery platforms, and the 2013 leak stream is converting once-secret capability architecture — FOXACID being a prime exhibit — into public material for defenders, vendors, and policymakers.