All Breaches
March 25, 2017 Verified Sensitive Record Healthcare Telemarketing

Health Now Networks Data Breach

The 2017 Health Now Networks exposed CRM dataset consists of files a researcher found through Shodan and reported on March 25, 2017. Direct inspection identified approximately 918,000 marketing or CRM lead records.

321.9 Thousand
Email Identifiers
12
Data Types
High
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

2 sensitive12
  • Health insurance information
  • Medical-supply or condition context
  • Names
  • Physical addresses
  • Dates of birth
  • Phone numbers
  • Email addresses
  • Social security numbers
  • Policy numbers
  • Telemarketing notes
  • Security questions and answers
  • Social connections

About This Breach

A developer said an old HealthNow CRM copy had been staged during a server move and mistakenly left in a root folder, then removed after contact from AWS. The exposure start, access logs, and number of third-party downloads remain unknown.

The broader files could contain names, addresses, dates of birth, phones, emails, Social Security and insurance or policy information, medical-supply or condition context, and telemarketing notes. Not every field was populated, and many SSN and policy values were missing, incorrect, or truncated. These were marketing leads from multiple sources, not insurer patient records.

A public breach source separately catalogues 321,920 unique emails and a broader set of normalized classes. Approximately 918,000 describes raw CRM rows, not people or patients, while 321,920 is a unique-email measure. No dataset or searchable person-level data has been imported locally.

The record does not identify anyone as a patient, customer, insured person, senior, caregiver, or person with a particular condition or policy. Health, insurance, SSN, security-answer, and relationship data must remain private. Unexpected medical-supply or insurance contact should be verified independently; correct personal or health details do not authenticate a caller.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information