How This Briefing Works
This report opens with key findings, then maps the gaps between what Leadfeeder 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
Leadfeeder was observed loading and executing before user consent was obtained on 61% of sites where it was detected.
Claims vs. Observed Behavior
account_surveillance
“Unknown - requires claims extraction”
C06+C07+C09+C14 detected - comprehensive B2B deanonymization platform
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Leadfeeder
- →IMMEDIATE: Audit complete Leadfeeder surveillance scope - catalog behavioral, recording, and identity capabilities
- →Map identity resolution methodology - IP lookup, reverse DNS, firmographic enrichment sources
- →Verify session recording extent - full interaction replay vs aggregated analytics
- →Enforce strict consent gate - account identification must not occur pre-consent
- →Document data flows to sales/marketing systems receiving deanonymized data
If You're Evaluating Leadfeeder
- →Evaluate first-party account identification alternatives
- →Consider form-based account capture instead of stealth visitor tracking
- →Investigate privacy-respecting B2B analytics without identity resolution
- →Prepare Leadfeeder removal plan - comprehensive surveillance may exceed acceptable risk
Negotiation Leverage
- →Leadfeeder deploys C06+C07+C09+C14 - vendor must explain comprehensive account identification surveillance
- →Demand complete technical disclosure of behavioral tracking, session recording, and identity resolution
- →Require consent-first operation - no pre-consent deanonymization
- →Negotiate removal of session recording if not contractually specified
- →Establish absolute liability for deanonymization violations under GDPR/CCPA
- →Consider contract termination if surveillance scope creates unacceptable compliance risk
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
Ignoring CMP signals
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 5 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
49 detection signatures across scripts, domains, cookies, and network endpoints