Ethereum Address
Detects Ethereum Address patterns.
- Type
- regex
- Engine
- universal
- Confidence
- medium
- Confidence justification
- Medium confidence: pattern has structural constraints but corroborative keywords are recommended to reduce false positive rates. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Not detected
- Jurisdictions
- global
- Regulations
- FATF Recommendations
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- financial
- Scope
- narrow
- Risk rating
- 7
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b0x[a-fA-F0-9]{40}\bCorroborative evidence keywords
identifier, number, ID, transaction, transfer, payment, deposit, withdrawal, debit, credit, data record, database record, record set, data extract, data export, database table, spreadsheet, data registry, registry entry, master data (+14 more)
Proximity: 300 characters
Should match
0x742d35Cc6634C0532925a3b844Bc9e7595f2bD28— Ethereum address0x0000000000000000000000000000000000000000— Zero address0xdAC17F958D2ee523a2206206994597C13D831ec7— USDT contract address format
Should not match
0x742d35Cc6634C0532925a3b844Bc9e7595f2bD2— Only 39 hex characters instead of 400x742d35Cc6634C0532925a3b844Bc9e7595f2bD289— 41 hex characters instead of 400xGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG— Contains invalid hex character Gtemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
- In English (as the primary international business language), standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.