All Vendors
deanon

Leadmagic

Leadmagic deanonymization platform initiates visitor identification before consent capture.

10 IOCs1 detections100% pre-consent1 sites
70
Vendor Risk Score

How This Briefing Works

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

1 detection across 1 site100% pre-consent activity
CRITICAL

Pre-Consent Activity

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

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps
Customer Impact

What This Means For You

Organizations using Leadmagic inherit deanonymization consent-timing liability. Privacy audits detecting pre-consent visitor identification create compliance exposure. Lead intelligence built on non-consented identity resolution produces legally questionable sales pipeline.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Leadmagic

  • →Implement consent gate before Leadmagic initialization
  • →Verify identification functionality with delayed post-consent loading
  • →Document consent timestamp vs deanonymization start for compliance records

If You're Evaluating Leadmagic

  • →Request Leadmagic consent integration documentation
  • →Evaluate visitor identification platforms with consent-first architecture
  • →Consider form-based lead capture eliminating stealth identification
  • →Investigate first-party identification alternatives

Negotiation Leverage

  • →Leadmagic executes pre-consent deanonymization - vendor must provide consent-aware initialization
  • →Require technical documentation of consent management integration
  • →Negotiate consent bridge implementation as contract requirement
  • →Establish liability terms for pre-consent visitor identification violations
Runtime Detections

Runtime Detections

1 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-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

8 INDICATORS

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

TRACK
*leadmagic.com/buVmOqQTd.js*
Tracking script
TRACK
leadmagic.com/buVmOqQTd.js
Auto-extracted from scan
Ecosystem

Ecosystem & Supply Chain

Operates within visitor identification and lead generation infrastructure. Pre-consent deployment suggests integration requiring immediate browser-side execution for real-time visitor tracking.
Loads (1)
Shopping Google
Evidence

Evidence Artifacts

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

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

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

Vendor Details