How This Briefing Works
This report opens with key findings, then maps the gaps between what ZendeskChat 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
ZendeskChat was observed loading and executing before user consent was obtained on 50% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Requires claims extraction via CDT”
Defeat device, behavioral biometrics, cross-domain sync, consent bypass, fingerprinting, persistence, and tag manager detected in runtime
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use ZendeskChat
- →Audit defeat device deployment within customer support infrastructure
- →Review behavioral biometrics scope in support interaction monitoring
- →Verify cross-domain sync boundaries for support continuity mechanisms
- →Audit tag manager capabilities for third-party script injection risk
- →Require consent collection before Zendesk tracking initialization
If You're Evaluating ZendeskChat
- →Customer support solutions without embedded visitor surveillance
- →Privacy-respecting helpdesk platforms limiting tracking scope
- →Self-hosted support infrastructure eliminating cross-customer intelligence leakage
Negotiation Leverage
- →Challenge defeat device mechanisms within customer service infrastructure
- →Require disclosure of all surveillance capabilities beyond support functionality
- →Demand opt-out from cross-customer support monitoring analysis
- →Request data processing agreement amendments addressing visitor tracking through support platform
- →Audit tag management capabilities for third-party data sharing risk
- →Negotiate liability indemnification for maximum tracking deployed through customer service infrastructure
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
Impact: Detection evasion mechanisms obscure surveillance deployment within customer support infrastructure.
Keystroke/mouse tracking
Impact: Interaction patterns with support interface captured to profile customer service engagement and predict support needs.
Identity stitching
Impact: Support interactions synchronized across organizational properties and external service touchpoints.
Ignoring CMP signals
Impact: Tracking mechanisms active through support infrastructure before visitor consent collection completes.
Device identification
Impact: Device characteristics harvested to maintain support continuity across sessions and identify returning visitors.
Long-lived identifiers
Impact: Long-lived tracking identifiers maintain support history beyond reasonable customer service timeframes.
Container/loader (neutral)
Impact: Tag management capabilities enable dynamic third-party script injection through support infrastructure.
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
257 detection signatures across scripts, domains, cookies, and network endpoints