How This Briefing Works
This report opens with key findings, then maps the gaps between what Exads 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
Exads was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown - requires claims extraction via CDT”
Runtime evidence shows C06/C09 patterns
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Exads
- →Audit RTB bidstream data exposure
- →Confirm consent before ad serving starts
- →Review vendor list: can you enumerate all auction participants?
If You're Evaluating Exads
- →Test page load: does Exads fire before consent banner?
- →Ask: what visitor data enters RTB bidstream?
- →Verify privacy policy discloses programmatic data sharing
Negotiation Leverage
- →C06 fingerprinting enables cross-site tracking. Is this disclosed in privacy policy?
- →C09 consent bypass: RTB auctions occur pre-consent. How do you enforce consent-first bidding?
- →Bidstream sharing = uncontrolled third-party data exposure. Can you provide exhaustive participant list?
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
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 3 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
84 detection signatures across scripts, domains, cookies, and network endpoints