Social EngineeringTechnologyInformationPhishingStolen CredentialsCustomer Data InvolvedTargetedPIIIdentity (basic)LowContained

Mediant Communications, LLC

bd_53318a9ba4214cdc · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 1, 2019

Filed

May 31, 2019

To disclose

9 weeks

Affected

260state residents only

Linked

9 filings

Confidence

65%

Full breach record for Mediant Communications, LLC →

Mediant Communications Inc. disclosed that on April 1, 2019, a malicious party gained unauthorized access to business email accounts via phishing, compromising investor information including names and addresses. The server was disconnected, law enforcement was notified, and 24 months of credit monitoring were offered.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 9 weeks / 60 days

Apr 1, 2019

Begins

Apr 1, 2019

Discovered

May 31, 2019

Filed

vs. sector median

10 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (8) · sorted by filing gap

South Carolina State AGbd_10fc27c51bae04a52019-05-31Verified
Delaware State AGbd_1512624e5ae85d132019-05-31Verified
California State AGbd_049c952e85b4826a2019-05-28 · +3dVerified
Massachusetts State AGbd_080ddf5dce6168ae2019-05-28 · +3dVerified

Show 4 more filings ↓up to 13d gap

Washington State AGbd_5318645d13786fb22019-05-28 · +3dCandidate
New Hampshire State AGbd_b1e8c5725e9a44402019-05-28 · +3dVerified
Oregon State AGbd_d1a9c1abb5ef26c62019-05-28 · +3dVerified
Hawaii State AGbd_24f3420b08bb89c72019-06-13 · +13dVerified

Name: Mediant Communications, LLC
norm: mediant communications

Name: Mediant Communications, LLC
norm: mediant communications
Industry: Technologyllm

Discovered: Apr 1, 2019
Breach occurred: Apr 1, 2019
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 260state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Reported the matter to law enforcement
Initial access: phishing_link

During the incident: Disconnected the affected email server from our system
Commenced an investigation to understand the nature and scope of the incident
Reported the matter to law enforcement
Updated network security controls and email system
Offering credit monitoring for a period of 24 months at no cost
Changes made: Updating network security controls and email system
Continuing to closely monitor and take further steps as appropriate to safeguard such information
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 9 filings · 9 states

View merged incident ↗

California State AGMay 28 · first

Massachusetts State AGMay 28 · first

Washington State AGMay 28 · first

New Hampshire State AGMay 28 · first

Oregon State AGMay 28 · first

South Carolina State AG+3d

Delaware State AG+3d

Montana State AG+3d · this page

Hawaii State AG+16d

Pattern: first filing May 28 (CA), last Jun 13 (HI) — a 16-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/Data-Breach-Sample-Letter-to-Consumer-1.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 31, 2019
Raw hash: f515bc479d7c4aa51e51aad04ce89a1a7a5487cae07244c80a3091214f6aef44

Linked disclosures

Regulatory filings (8) · sorted by filing gap

Reporting entityMediant Communications, LLC

Victim entityMediant Communications, LLC

Incidentdiscovered Apr 1, 2019

Stated responseDisconnected the affected email server from our system

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov