Bitcoin Address (Bech32)
Detects Bitcoin Address (Bech32) 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
- Verified
- Jurisdictions
- global
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- financial
- Scope
- narrow
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\bbc1[a-zA-HJ-NP-Z0-9]{25,39}\bCorroborative evidence keywords
identifier, number, ID, transaction, transfer, payment, deposit, withdrawal, debit, credit, field, column, row, entry, record, value, form, register, database, extract (+16 more)
Proximity: 300 characters
Should match
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4— Bech32 Bitcoin addressbc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq— Standard Bech32 addressbc1q0000000000000000000000000000000000— Minimal Bech32 address
Should not match
bc2qw508d6qejxtdg4y5r3zarvary0c5xw7k— Wrong prefix (bc2 instead of bc1)bc1qw508d6qejxtdg4y5r3zarv— Too short (only 22 characters after bc1)tb1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4— Testnet prefix (tb1 instead of bc1)template 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.