IMEI

Name: IMEI
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Detects IMEI patterns.

Type: regex
Engine: universal
Confidence: medium
Confidence justification: Medium confidence: validated with Luhn algorithm and supported by corroborative keyword evidence.
Detection quality: Verified
Jurisdictions: global
Regulations: GDPR
Frameworks: CIS Controls, ISO 27001, NIST CSF, SOC 2
Data categories: device-id
Scope: specific
Risk rating: 5
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\b\d{15}\b

Corroborative evidence keywords

device, identifier, serial number, hardware, fax, facsimile, toll free, hotline, helpline, [object Object], [object Object], country code, area code, extension, ext

Proximity: 300 characters

Should match

353456789012348 — Exact 65 probe - Luhn-valid IMEI candidate without a label
IMEI: 490154203237518 — Exact 75 probe - Luhn-valid labelled IMEI without a device record
Handset inventory device assignment - IMEI: 860000000000009; subscriber account and blacklist status recorded. — Exact 85 probe - Luhn-valid IMEI plus handset and subscriber record

Should not match

35345678901234 — Only 14 digits instead of 15
3534567890123456 — 16 digits instead of 15
35345678901234A — Contains a letter instead of all digits
353456789012345 — Adversarial 15-digit candidate with an invalid Luhn check digit
Public manufacturer guide - IMEI: 353456789012348 — Public guide contains a complete labelled candidate
Template example: handset inventory device assignment IMEI 490154203237518 with subscriber account and blacklist status. — Template contains otherwise high-tier evidence

Known false positives

Technical identifiers appearing in public documentation, network configuration guides, or example configurations without representing actual infrastructure. Mitigation: Cross-reference with known documentation patterns and reserved address ranges. Require proximity to infrastructure-specific context.
Placeholder and example values commonly used in technical tutorials and vendor documentation. Mitigation: Maintain exclusion lists for well-known example values (RFC 5737 documentation addresses, example MAC addresses).

Collections

Network & Device Identifiers