How This Briefing Works
This report opens with key findings, then maps the gaps between what Signalhire 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
Signalhire was observed loading and executing before user consent was obtained on 94% of sites where it was detected.
Claims vs. Observed Behavior
comprehensive_identification
“Pending claims extraction”
Runtime shows all 6 threat codes active simultaneously for maximum de-anonymization
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Signalhire
- →Immediate audit of all Signalhire contracts for consent and privacy language
- →Map complete identity resolution flow from anonymous visit to revealed identity
- →Calculate total exposure from persistent cross-session identification
- →Document consent bypass scope across all six identification components
- →Assess competitive intelligence risk from de-anonymized visitor list exposure
If You're Evaluating Signalhire
- →This should not be in evaluation. This should be in removal planning.
- →If legally required: Demand consent-first activation with ZERO pre-consent identification
- →Require written confirmation that NO identified visitor data accessible to competitors
- →Negotiate unlimited liability coverage for regulatory penalties from detected violations
- →Alternative: First-party identification via authenticated sessions eliminates vendor dependency and consent bypass
Negotiation Leverage
- →Six active BTI codes: This is maximum de-anonymization threat profile
- →C09 across ALL components: Demand DPA rewrite requiring consent-first activation or accept unlimited liability
- →C14+C13 combination: This is purpose-built surveillance infrastructure, not analytics tooling
- →Broker exposure: Require written confirmation that NO de-anonymized visitor data enters ANY platform accessible to competitors
- →C07+persistence: Demand immediate visitor data deletion upon consent revocation, covering ALL identification data
- →If renewal required: Treat as comprehensive identification infrastructure with maximum privacy impact
- →Alternative: Authenticated first-party identification eliminates third-party surveillance dependency
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
Long-lived identifiers
PII deanonymization
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
23 detection signatures across scripts, domains, cookies, and network endpoints