How This Briefing Works
This report opens with key findings, then maps the gaps between what Cookiebot 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
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
Runtime analysis needed to confirm exact pre-consent cookie behavior and timing, server endpoints contacted before consent, TCF string propagation to downstream vendors, data payloads in network requests, and behavior differences between TCF-enabled and standalone configurations.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Cookiebot
- →- Audit Cookiebot's pre-consent network requests using HAR capture to identify exactly what data is transmitted before any consent choice is made. - Evaluate whether TCF integration is enabled and, if so, inventory every vendor receiving consent strings through the framework. - Request Cookiebot's current Data Processing Agreement and verify the legal basis for any data transfers to US-based infrastructure. - Consider whether a self-hosted or server-side consent solution would eliminate the pre-consent JavaScript execution risk. - Document Cookiebot's own cookie footprint (CookieConsent, CookiebotConsent, etc.) and include it in your organization's cookie disclosure.
Negotiation Leverage
- →Cookiebot's primary leverage point is the Wiesbaden court ruling — any organization deploying Cookiebot should understand that a German court found the platform's data transfer practices violate GDPR. Ask Cookiebot for written guarantees about server location and data residency. Demand documentation of exactly which cloud providers process visitor data and under which jurisdictions. If TCF is enabled, require a list of all vendors receiving consent strings and evidence that those vendors actually check consent before processing. The Belgian DPA's finding that TCF itself violates GDPR is a strong negotiation tool — Cookiebot cannot guarantee compliance through a framework regulators have already deemed noncompliant. Use this to negotiate data processing terms, request contractual indemnification for consent failures, or justify switching to a CMP that does not depend on the TCF framework.
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.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Impact: IAB TCF integration generates TC Strings encoding visitor consent choices and shares them with every TCF-registered vendor on the page. Adalytics research showed many vendors do not check these signals before processing data.
Full session replay
Identity stitching
Ignoring CMP signals
Impact: Cookiebot JavaScript executes before any consent is collected. Sets identification cookies (CookieConsent, CookiebotConsent) and communicates with external servers pre-consent. The consent tool itself operates without consent.
Device identification
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
273 detection signatures across scripts, domains, cookies, and network endpoints