All Vendors
data_enrichment

Reversecontact

Reversecontact operates as enrichment infrastructure with cross-domain synchronization and consent bypass. Augments visitor records with third-party data while syncing identity across domains before consent resolution.

6 IOCs27 detections7% pre-consent25 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Reversecontact 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

Key Findings

27 detections across 25 sites7% pre-consent activity
MEDIUM

Pre-Consent Activity

Reversecontact was observed loading and executing before user consent was obtained on 7% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps

enrichment_sync

HIGH
They Claim

“Pending claims extraction”

Observed Behavior

Runtime shows cross-domain enrichment sync before consent

Customer Impact

What This Means For You

Marketing teams gain enriched visitor profiles but expose augmented data through cross-domain sync (Broker). Legal teams face consent bypass liability from pre-consent enrichment processing. RevOps must map cross-domain data flow to assess competitive intelligence exposure.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Reversecontact

  • →Audit enrichment timing and cross-domain sync against consent framework
  • →Map domain topology and enrichment data flow
  • →Verify DPA covers third-party data sources used in enrichment

If You're Evaluating Reversecontact

  • →Require consent-first enrichment with cross-domain sync disabled pre-consent
  • →Demand disclosure of enrichment data sources and sync domain scope
  • →Negotiate data isolation preventing enriched profile exposure to external domains

Negotiation Leverage

  • →C08+C09 enrichment threat: Demand DPA rewrite requiring consent before enrichment and sync
  • →Request list of ALL third-party data sources AND domains receiving enriched profiles
  • →Require audit rights covering enrichment methodology and cross-domain data flow
  • →Negotiate retention limits for enriched visitor data
Runtime Detections

Runtime Detections

2 BTI-C CODES

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.

BTI-C08Cross-Domain Sync

Identity stitching

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

4 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Reversecontact operates in enrichment layer, receiving visitor signals from identification vendors and feeding enriched profiles to marketing automation and CRM via cross-domain sync. Creates exposure when enrichment occurs before consent and syncs to multiple domains accessible to external parties.
Loads (2)
LinkedinSegment
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

6 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details