How This Briefing Works
This report opens with key findings, then maps the gaps between what Openmart 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
Openmart was observed loading and executing before user consent was obtained on 7% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Broker score (25) and Counselor score (55) indicate data sharing and consent violations. Privacy policy likely lacks disclosure of session recording and persistent identifier usage.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Openmart
- →Implement consent gate before Openmart scripts activate
- →Audit session recording scope to confirm PII handling compliance
- →Review Data Processing Agreement for enrichment data sharing and retention terms
- →Confirm privacy policy discloses visitor profiling and session recording practices
If You're Evaluating Openmart
- →Defer Openmart scripts until post-consent confirmation
- →Require vendor documentation on data source transparency and lawful collection basis
- →Assess first-party enrichment alternatives using consented customer data only
- →Demand technical controls for persistent identifier lifespan limits
Negotiation Leverage
- →Openmart contract may permit enrichment data resale or cross-customer benchmarking - demand opt-out and data isolation
- →Session recordings and persistent profiles may be retained indefinitely - negotiate strict retention limits
- →Confirm enrichment data is not sold to third-party data brokers or shared with competitors
- →Request evidence of GDPR Article 6 lawful basis for session recording and persistent tracking
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.
Full session replay
Ignoring CMP signals
Container/loader (neutral)
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
7 detection signatures across scripts, domains, cookies, and network endpoints