CONNECTICUTSocial EngineeringHealthcareHealthcarePhishingStolen CredentialsCustomer Data InvolvedMulti-Stage ChainPHIHealth (basic)Identity (basic)Government IDMediumResolved

Middlesex Hospital

bd_2bec0a6df1f2121b · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Dec 4, 2015

To disclose

—

Affected

946

Confidence

68%

Full breach record for Middlesex Hospital →

Middlesex Hospital reported to HHS on 2015-12-04 a Hacking/IT Incident affecting 946 individuals. Breached information located on Email. Employees responded to a phishing email, leading to PHI disclosure including names, addresses, DOB, and SSNs. Remediation included phishing training, credit monitoring, and security upgrades.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Dec 4, 2015

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed946 affectedView incident

Name: Middlesex Hospital
norm: middlesex hospital
Industry: Health Care Services

Name: Middlesex Hospital
norm: middlesex hospital
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 946nationwide
Data types: PHIHealth (basic)Identity (basic)Government ID
HHS breach type: Hacking / IT incident
Where the data lived: Email
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Provided breach notification to HHSOCR obtained assurances that the CE implemented the corrective action steps listed above
Initial access: phishing_link

During the incident: Set up a dedicated call center to answer questions for affected individuals
Provided affected individuals with 12 months of credit monitoring services at no cost
Developed a mandatory Phishing Awareness and Response Training program for employees
Required additional training for all supervisors and managers to provide to their staff
Designated March as “Cyber Awareness” month
Procured a vendor to conduct social engineering testing
Upgraded its anti-virus program
Utilized the security reporting tool it had purchased
Changes made: Developed a mandatory Phishing Awareness and Response Training program for employees
Required additional training for all supervisors and managers to provide to their staff
Designated March as “Cyber Awareness” month
Procured a vendor to conduct social engineering testing to assess the effectiveness of the CE's staff training
Upgraded its anti-virus program
Utilized the security reporting tool it had purchased
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

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: Dec 4, 2015
Raw hash: 9fc71bf67d250e987bf98559720f395f412cbafc12e2b13f264c2d5a5bcd10a0

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/html2.3 KB

Download View at source

Reporting entityMiddlesex Hospital

Victim entityMiddlesex Hospital

IncidentUnauthorized Access

Stated responseSet up a dedicated call center to answer questions for affected individuals

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing