HackingHealthcareHealthcareStolen CredentialsData ExfiltratedIdentity (basic)Financial accountLowContained

AliMed

bd_91191e2c2d2c9522 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 27, 2020

Filed

Aug 28, 2020

To disclose

5 weeks

Affected

121state residents only

Linked

7 filings

Confidence

65%

Full breach record for AliMed →2 incidents on file

AliMed, Inc. disclosed unauthorized access to a server potentially acquiring payment card data (names, card numbers, CVVs) for transactions between June 1, 2019, and June 17, 2020. The incident was discovered on July 27, 2020. Notices were sent on August 26, 2020. Forensic investigators were engaged.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 422 days

discovery → filing · 5 weeks / 32 days

Jun 1, 2019

Begins

Jul 27, 2020

Discovered

Aug 28, 2020

Filed

vs. sector median

5 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Massachusetts State AGbd_156a767e28b472922020-08-28Verified
California State AGbd_462665e14884d2b92020-08-28Verified
Washington State AGbd_63fba7c990b626742020-08-28Candidate
Oregon State AGbd_f05113466b99315e2020-08-28Verified

Show 2 more filings ↓up to 7d gap

Indiana State AGbd_aae2cdb2fda156a72020-08-27 · +1dVerified
New Hampshire State AGbd_c8d2918e468c9dfa2020-09-04 · +7dVerified

Name: AliMed
norm: alimed
Domain: alimed.com

Name: AliMed
norm: alimed
Domain: alimed.com
Industry: Healthcarellm

Discovered: Jul 27, 2020
Breach occurred: Jun 1, 2019 – Jun 17, 2020
Undetected for: 422 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 26, 2020
Affected individuals: 121state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Engaged external forensic investigators and data privacy professionals
Commenced a prompt and thorough investigation
Implemented enhanced security safeguards
Conducting ongoing monitoring of our network
Changes made: Implemented enhanced security safeguards
Conducting ongoing monitoring of our network
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(32 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 · 7 states

View merged incident ↗

Indiana State AGAug 27 · first

Massachusetts State AG+1d

California State AG+1d

Washington State AG+1d

Oregon State AG+1d

Montana State AG+1d · this page

New Hampshire State AG+8d

Pattern: first filing Aug 27 (IN), last Sep 4 (NH) — a 8-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://dojmt.gov/wp-content/uploads/AliMed-Inc-Consumer-ltr.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 28, 2020
Raw hash: 55efabfb1ea41426623624c992eca70d184ce9d0d63940aa2af48fcf20708139

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityAliMed

Victim entityAliMed

Incidentdiscovered Jul 27, 2020

Stated responseEngaged external forensic investigators and data privacy professionals

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov