COLORADOSocial EngineeringHealthcareHealthcarePhishingStolen CredentialsCustomer Data InvolvedData ExfiltratedPHIHealth (basic)Identity (basic)MediumResolved

Metro Community Provider Network

bd_12b663d1ba3c5441 · schema v1 · pii pii-v1

Severity

Medium

Financial impact

$400K

Discovered

Jan 27, 2012

Filed

Jan 27, 2012

To disclose

—

Affected

3,200

Linked

2 filings

Confidence

70%

Full breach record for Metro Community Provider Network →

Metro Community Provider Network reported to HHS on 2012-01-27 a Hacking/IT Incident affecting 3200 individuals. Breached information located on Email. A hacker accessed employee email accounts via phishing to obtain ePHI.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS report on time

⚠ filing dateThe stored discovery date equals the regulator filing date, so no genuine detection date was captured.

Incident timeline

discovery → filing · ≤1 day / 0 days

Jan 27, 2012

Discovered

Jan 27, 2012

Filed

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCR enforcementbd_28e47cab7765d74f2017-04-12 · +1902dVerified by operator

Name: Metro Community Provider Network
norm: metro community provider network
Industry: Health Care Services

Name: Metro Community Provider Network
norm: metro community provider network
Industry: Healthcaresource default

Discovered: Jan 27, 2012
Materiality determined: —
Notification sent: —
Affected individuals: 3,200nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incidentOther
Where the data lived: Email
Covered-entity type: Healthcare provider
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid AccountsT1114 Email Collection
Threat actor: ExternalFinancial
Regulator citations: Notified HHS OCRSettled potential noncompliance with HIPAA Privacy and Security Rules
Initial access: phishing_link

During the incident: Took necessary corrective action related to the phishing incident
Conducted a risk analysis
Implemented a corrective action plan
Changes made: Implemented a corrective action plan
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS report on timeHHS notified
Discovery-date grounding: filing dateThe stored discovery date equals the regulator filing date, so no genuine detection date was captured.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: Jan 27, 2012
→ Notified: not extracted
— 60 days HHS report on time
HIPAA
Discovered: Jan 27, 2012
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: Jan 27, 2012 → Notified: not extracted	—	60 days	HHS report on time
HIPAA	Discovered: Jan 27, 2012 → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

HHS OCRJan 27 · first · this page

HHS OCR enforcement+1902d

Pattern: first filing Jan 27 (CO), last Apr 12 — a 1902-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jan 27, 2012
Raw hash: 5d8338df33f0ffe57b09ed5c5a7f26361a83a6a32a99c75eab17e03a189fd9d5

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html3.3 KB

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityMetro Community Provider Network

Victim entityMetro Community Provider Network

Incidentdiscovered Jan 27, 2012

Stated responseTook necessary corrective action related to the phishing incident

ComplianceHHS report on time

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing