How This Briefing Works
This report opens with key findings, then maps the gaps between what Silktide 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
Silktide was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
compliance_surveillance
“Pending claims extraction”
Runtime shows accessibility testing infrastructure deploying comprehensive tracking before consent
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Silktide
- →Audit accessibility testing scope - verify separation from behavioral tracking
- →Map consent bypass justification - does accessibility require pre-consent activation
- →Document cross-domain sync scope and visitor data exposure
- →Verify DPA distinguishes accessibility testing from behavioral surveillance
If You're Evaluating Silktide
- →Require consent-first behavioral tracking with accessibility testing isolated
- →Demand technical proof that accessibility compliance requires consent bypass
- →Negotiate data isolation ensuring accessibility testing separate from visitor surveillance
- →Evaluate accessibility alternatives without behavioral tracking extension
Negotiation Leverage
- →Five active BTI codes: Demand DPA addressing each threat category
- →C09 accessibility justification: Require technical validation that compliance testing necessitates consent bypass
- →C07+C08 tracking extension: Accessibility testing should not require session recording or cross-domain visitor sync
- →Request written confirmation that accessibility data remains isolated from behavioral analytics
- →Alternative: Accessibility testing without behavioral tracking eliminates surveillance surface while maintaining compliance
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
Identity stitching
Ignoring CMP signals
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
78 detection signatures across scripts, domains, cookies, and network endpoints