How This Briefing Works
This report opens with key findings, then maps the gaps between what Quantcast discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Pre-Consent Activity
Quantcast was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
comprehensive_surveillance
“Pending claims extraction”
Runtime shows all 6 threat codes active simultaneously before consent
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Quantcast
- →Immediate audit of all Quantcast contracts for consent language
- →Map complete data flow including bidstream participants
- →Calculate total exposure from persistent cross-domain tracking
- →Document consent bypass timing across all components
If You're Evaluating Quantcast
- →This should not be in evaluation. This should be in removal planning.
- →If required for measurement: Demand consent-first activation with ZERO pre-consent processing
- →Require bidstream exclusivity preventing competitor access
- →Negotiate liability caps covering regulatory penalties from detected violations
Negotiation Leverage
- →Six active BTI codes: This is the threat profile BLACKOUT was built to expose
- →C09 across ALL components: Demand DPA rewrite requiring consent-first activation or accept unlimited liability
- →C07+C08+C13: Require complete visitor data deletion within 24hr of revoked consent
- →Broker exposure: Demand written confirmation that NO visitor data enters bidstream accessible to competitors
- →If renewal required: Treat as comprehensive surveillance infrastructure, not measurement tool
- →Alternative: Replace with consent-respecting measurement (Plausible, Fathom) + first-party attribution
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Long-lived identifiers
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
76 detection signatures across scripts, domains, cookies, and network endpoints