HackingTechnologyInformationStolen CredentialsTargetedGovernment IDFinancial accountMediumContained

SuccessfulMatch.com

bd_8a0ba18d038d2f64 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 18, 2022

Filed

Sep 13, 2022

To disclose

26 weeks

Affected

2state residents only

Confidence

66%

Full breach record for SuccessfulMatch.com →

SuccessfulMatch.com notified Montana residents of a data security incident occurring on March 18, 2022. A user accessed personal information via a web crawler and notified the company. Exposed data included SSNs, Tax IDs, and account numbers. The company remediated the vulnerability and engaged third-party security experts.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 26 weeks / 179 days

Mar 18, 2022

Begins

Mar 18, 2022

Discovered

Sep 13, 2022

Filed

vs. sector median

+7 wks slower

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

Name: SuccessfulMatch.com
norm: successfulmatchcom
Domain: successfulmatch.com

Name: SuccessfulMatch.com
norm: successfulmatchcom
Domain: successfulmatch.com
Industry: Technologyllm

Discovered: Mar 18, 2022
Breach occurred: Mar 18, 2022
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 2state-resident count only
Data types: Government IDFinancial account
Data elements: Social Security number
Attack vector: Unauthorized Access
MITRE ATT&CK: T1595 Active ScanningT1119 Automated Collection
Threat actor: External
Initial access: exploit_public_facing

During the incident: Identified the vulnerability associated with this Web Crawler Incident
Taken action to remedy the identified vulnerability
Taken steps to ensure that the pages that contained the applicable personal information were scrubbed of information
Patched any issues which would prevent any future web crawlers from accessing this information
Partnered with a third-party information and data security company to scan our website for vulnerabilities and upgrade or improve our software or systems
Hired security experts to monitor our system for more possible security bugs
Improved our internal policy to encourage our engineers to spot more possible security bugs
Changes made: Patched issues to prevent future web crawler access
Scrubbed pages containing personal information
Partnered with third-party security company to scan website and upgrade systems
Hired security experts to monitor system for security bugs
Improved internal policy to encourage engineers to spot security bugs
Source: Quoted from the filing itself, not independently verified.

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

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://dojmt.gov/wp-content/uploads/OCP/Consumer-Notification-Letter-561.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 13, 2022
Raw hash: 495c42ef05a6a73c8dedb95ed3f185101fbf200f6dd49b743dfaf08154419855

Reporting entitySuccessfulMatch.com

Victim entitySuccessfulMatch.com

Incidentdiscovered Mar 18, 2022

Stated responseIdentified the vulnerability associated with this Web Crawler Incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov