How This Briefing Works
This report opens with key findings, then maps the gaps between what Rockerbox 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
Rockerbox was observed loading and executing before user consent was obtained on 7% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown”
Requires claims extraction via CDT
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Rockerbox
- →Audit consent implementation - verify tracking starts AFTER opt-in
- →Request data processing addendum with cross-domain tracking limitations
- →Implement server-side attribution as alternative to client-side fingerprinting
- →Monitor blocking rates via Privacy Sandbox APIs to quantify signal loss
If You're Evaluating Rockerbox
- →Server-side attribution platforms (Northbeam, Hyros)
- →First-party data warehousing with custom attribution models
- →Privacy-preserving attribution (Google Privacy Sandbox Aggregate API)
Negotiation Leverage
- →Attribution accuracy depends on tracking coverage - ask vendor to quantify signal loss from privacy controls
- →DPA must restrict cross-customer data use - your prospects should not train competitor models
- →Require consent-first architecture or contract limits liability transfer
- →Platform creates measurement distortion AND CAC subsidy - price should reflect dual 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.
Evasion infrastructure, auditor bypass
Identity stitching
Impact: Cross-site tracking enables profile building across properties without user knowledge, triggering GDPR Article 35 (DPIA requirement).
Ignoring CMP signals
Impact: Tracking initiates before consent collection, creating liability for unlawful processing under Article 6 GDPR.
Device identification
Impact: Browser fingerprinting without consent violates ePrivacy Directive. Creates enforceable violations under GDPR Article 21 (right to object).
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
116 detection signatures across scripts, domains, cookies, and network endpoints