How This Briefing Works
This report opens with key findings, then maps the gaps between what Blackwoodseven 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
Blackwoodseven was observed loading and executing before user consent was obtained on 4% of sites where it was detected.
Consent Bypass
8 vendors fire pre-consent including Bytemine, Leadfeeder, Scoreplex, HubSpot, YouTube
Vendor Disclosure Gap
Cookie policy lists ~9 vendors but 37 distinct vendors detected
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
Claims vs. Observed Behavior
Consent Bypass
“GDPR/CCPA compliant with cookie consent mechanism”
8 vendors fire pre-consent including Bytemine, Leadfeeder, Scoreplex, HubSpot, YouTube
intel_detections shows pre_consent=true for 8 distinct vendors on blackwoodseven.com scans
Vendor Disclosure Gap
“Cookie policy lists third-party vendors”
Cookie policy lists ~9 vendors but 37 distinct vendors detected
Comparison of cookie policy vendors vs intel_detections vendor_slug count
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Blackwoodseven
- →Audit what data Blackwood Seven's HamiltonAI platform collects from your properties and where it flows within Kantar
- →Review your DPA to ensure it covers the actual 37-vendor ecosystem, not just the 9 disclosed in their cookie policy
- →Implement consent gating for any Blackwood Seven scripts to prevent pre-consent data collection
- →Request documentation on data flows between Blackwood Seven, Kantar, and Bain Capital portfolio companies
If You're Evaluating Blackwoodseven
- →Request Blackwood Seven's complete vendor and subprocessor list before any engagement
- →Verify whether HamiltonAI platform data stays within Blackwood Seven or flows to parent company Kantar
- →Compare marketing mix modeling alternatives that do not carry conglomerate data aggregation risk
- →Require contractual restrictions on data usage beyond your specific attribution use case
Negotiation Leverage
- →Cookie policy undercount: 37 vendors detected vs. 9 disclosed — a 4x gap demonstrating systematic disclosure failures; use this to negotiate complete vendor transparency as a contract condition
- →Pre-consent vendor firing: 8 vendors including Leadfeeder, HubSpot, and YouTube fire before consent — leverage this to require consent architecture improvements in any implementation
- →Kantar subsidiary risk: As a Kantar/Bain Capital entity, data flows may extend beyond Blackwood Seven — negotiate explicit restrictions on data sharing within the Kantar corporate family
- →Leadfeeder pre-consent: B2B visitor identification fires before consent, exposing corporate visitor data — use this to negotiate removal of identity resolution vendors from your deployment
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
Full session replay
Ignoring CMP signals
Device identification
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
159 detection signatures across scripts, domains, cookies, and network endpoints