How This Briefing Works
This report opens with key findings, then maps the gaps between what Builtwith 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
Builtwith was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
consent
“Pending claims extraction via CDT”
Consent bypass during technology profiling detected
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Builtwith
- →Configure BuiltWith to activate only after consent for analytics/profiling collected
- →Verify technology detection occurs server-side (not client-side visitor tracking)
- →Limit BuiltWith use to internal competitive analysis (not visitor-facing deployments)
If You're Evaluating Builtwith
- →Request DPA confirming site profiling data is not used for visitor identification
- →Verify BuiltWith does not deploy client-side tracking for technology detection
- →Assess whether BuiltWith deployment is necessary vs. server-side technology detection alternatives
Negotiation Leverage
- →BuiltWith consent bypass (BTI-C09) during profiling creates pre-consent intelligence gathering—clarify whether deployment is server-side (competitive analysis) or client-side (visitor tracking)
- →If client-side deployment: require technical controls to delay profiling until after consent collection
- →If server-side deployment: verify no visitor-level data collection or retention
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.
Ignoring CMP signals
Impact: Initiates technology profiling and site fingerprinting before consent collection, creating automatic legal violations for intelligence gathering processes.
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
20 detection signatures across scripts, domains, cookies, and network endpoints