How This Briefing Works
This report opens with key findings, then maps the gaps between what Emarsys 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
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Web Extend SDK pre-consent loading behavior”
Awaiting scanner verification of scarab-v2.js initialization timing relative to consent signals
pending
“SAP ecosystem data flow mapping”
Third-party data enrichment flows through SAP Customer Data Platform integrations require runtime confirmation
pending
“Cookie persistence and cross-domain tracking”
Cookie mechanisms and cross-domain behavioral linking need forensic analysis
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Emarsys
- →- Audit whether Emarsys Web Extend (scarab-v2.js / scarabresearch.com) loads before consent is granted on sites you interact with - Review data processing agreements to understand how behavioral data flows through SAP's Customer Data Platform integrations - Assess whether the 100+ partner ecosystem creates unacceptable data sharing exposure for your organization - Monitor for cross-domain tracking between SAP-connected properties that may link your behavioral profiles - Request disclosure of all third-party data enrichment partners that receive your interaction data
Negotiation Leverage
- →Emarsys is a mature SAP-owned platform with enterprise-grade capabilities, but the depth of behavioral data collection and breadth of the SAP ecosystem create significant data flow complexity. Key leverage points: (1) Pre-consent loading patterns — if Web Extend fires before consent, this is a regulatory liability for the deploying site. (2) SAP ecosystem data flows — demand clarity on exactly which SAP products and third-party partners receive behavioral data. (3) The scarabresearch.com CDN domain is a legacy artifact that obscures the SAP/Emarsys relationship in network traffic, making informed consent more difficult for end users.
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
89 detection signatures across scripts, domains, cookies, and network endpoints