MalwareTechnologyHealthcareInformationRansomwareCapture Stored DataData ExfiltratedData EncryptedCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDHealth (basic)Financial accountFinancial credentialsMediumContained

CodeMetro

bd_f125821bfab468fd · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 21, 2020

Filed

Jun 19, 2020

To disclose

8 weeks

Affected

Not disclosed

Linked

7 filings

Confidence

64%

Full breach record for CodeMetro →3 incidents on file

CodeMetro suffered a ransomware attack on April 21, 2020, which resulted in the exfiltration of patient and employee data including SSNs, health information, and financial details. The incident was detected within hours, law enforcement was notified, and forensic investigators were engaged. Affected individuals were offered one year of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 8 weeks / 59 days

Apr 21, 2020

Begins

Apr 21, 2020

Discovered

Jun 19, 2020

Filed

vs. sector median

10 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Indiana State AGbd_0d4f8b16d4ab2cef2020-06-19Verified
California State AGbd_57b00b16078461a82020-06-19Candidate
Massachusetts State AGbd_775ef4afeec2ac602020-06-19Verified
New Hampshire State AGbd_8a2e4358507c5d632020-06-19Verified

Show 2 more filings ↓up to 3d gap

HHS OCRbd_e29634f20cc85d4d2020-06-19Verified
California State AGbd_78748fa912bcc6a72020-06-16 · +3dVerified

Name: CodeMetro
norm: codemetro
Domain: codemetro.com

Name: CodeMetro
norm: codemetro
Domain: codemetro.com
Industry: TechnologyllmHealthcarellm

Discovered: Apr 21, 2020
Breach occurred: Apr 21, 2020
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 29, 2020
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDHealth (basic)Financial accountFinancial credentials
Data elements: Social Security numberDate of birth
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 ChannelT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: notified federal law enforcement authorities

During the incident: Took immediate steps to contain the threat
Engaged a third-party forensic firm to investigate the incident and assist with remediation efforts
Notified federal law enforcement authorities of the incident
Promptly launched a forensic investigation
Contacted law enforcement
Took steps to remediate the incident
Enhanced our security and monitoring
Hardened our systems to minimize the risk of any similar incident in the future
Offered you credit monitoring for a period of one year, at no cost to you, through TransUnion
Changes made: Enhanced our security and monitoring
Hardened our systems to minimize the risk of any similar incident in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 weeks(59 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 5 states

View merged incident ↗

California State AGJun 16 · first

Indiana State AG+3d

California State AG+3d

Massachusetts State AG+3d

New Hampshire State AG+3d

HHS OCR+3d

Montana State AG+3d · this page

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://dojmt.gov/wp-content/uploads/OCP/General-Notice-109.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 19, 2020
Raw hash: 83bee8c5280ec12789a8e9b02aa4b291cc536cc1cea4d48e09e8ae8eb0c75877

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityCodeMetro

Victim entityCodeMetro

Incidentdiscovered Apr 21, 2020

Stated responseTook immediate steps to contain the threat

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov