How This Briefing Works
This report opens with key findings, then maps the gaps between what Kiosked 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
Kiosked was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
consent_timing
“Unknown - requires claims extraction”
C09 consent bypass observed in runtime deployment
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Kiosked
- →Implement consent gate before Kiosked initialization
- →Verify ad serving functionality with post-consent loading
- →Document consent timestamp vs Kiosked execution for audit trail
If You're Evaluating Kiosked
- →Request Kiosked consent integration documentation
- →Evaluate advertising platforms with native consent-first architecture
- →Consider server-side ad decisioning to eliminate browser consent requirements
Negotiation Leverage
- →Kiosked executes pre-consent - vendor must provide consent-aware initialization
- →Require technical documentation of consent management integration capabilities
- →Negotiate consent bridge implementation as contract requirement
- →Establish liability terms for pre-consent tracking violations
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.
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
16 detection signatures across scripts, domains, cookies, and network endpoints