All Vendors
platform

Dappradar

Dappradar (blockchain/Web3 analytics) exhibits consent bypass (C09) and aggressive persistence (C13). Tracking continues across wallet interactions and chain activity.

10 IOCs25 detections4% pre-consent24 sites
70
Vendor Risk Score

How This Briefing Works

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

25 detections across 24 sites4% pre-consent activity
MEDIUM

Pre-Consent Activity

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

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps

pending

UNKNOWN
They Claim

“Unknown - requires claims extraction via CDT”

Observed Behavior

Runtime evidence shows C09/C13 patterns

Customer Impact

What This Means For You

Wallet address = personal data under GDPR if linked to identifiable individual. Web3 tracking creates permanent record (blockchain immutability) + traditional web tracking. Deletion requests become impossible once on-chain.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Dappradar

  • →Audit what data associates with wallet addresses
  • →Confirm consent before wallet connection triggers tracking
  • →Review data retention: can you delete wallet-associated analytics?

If You're Evaluating Dappradar

  • →Test wallet connection flow: does tracking start before consent?
  • →Check localStorage/IndexedDB for persistent identifiers
  • →Verify privacy policy addresses blockchain data persistence

Negotiation Leverage

  • →C13 persistence via localStorage survives cookie deletion. How do users exercise deletion rights?
  • →Wallet address correlation = on-chain/off-chain identity graph. Is this disclosed in privacy policy?
  • →C09 consent bypass observed. What technical controls prevent tracking before wallet consent?
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-C09Consent Bypass

Ignoring CMP signals

BTI-C13Persistence Mechanisms

Long-lived identifiers

IOC Manifest

IOC Manifest

7 INDICATORS

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

TRACK
*dappradar.com/cdn-cgi/challenge-platform/h/b/orchestrate/chl_page/v1*
Tracking script
TRACK
dappradar.com/cdn-cgi/challenge-platform/h/b/orchestrate/chl_page/v1
Auto-extracted from scan
Ecosystem

Ecosystem & Supply Chain

Crypto/Web3 analytics stack. Often paired with wallet connectors (MetaMask, WalletConnect) and DeFi platforms. On-chain activity correlation creates unique deanonymization risk.
Loads (1)
Cloudflare Insights
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