HackingTechnologyInformationCustomer Data InvolvedPIIIdentity (basic)Financial accountPCILowContained

EventConnect

bd_0f31cac49a0926b4 · schema v1 · pii pii-v1

Severity

Low

Discovered

May 30, 2025

Filed

Jul 11, 2025

To disclose

6 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

65%

Full breach record for EventConnect →

EventConnect experienced unauthorized access to its platform between May 28 and June 2, 2025. The incident exposed hotel reservation data including names, addresses, phone numbers, and emails, with potential exposure of payment card numbers (excluding CVVs). EventConnect detected the activity on May 30, 2025, engaged forensic specialists, secured the platform, and notified affected individuals, offering 24 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 2 days

discovery → filing · 6 weeks / 42 days

May 28, 2025

Begins

May 30, 2025

Discovered

Jul 11, 2025

Filed

vs. sector median

13 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Iowa State AGbd_7a1c1c5c0cef36662025-07-07 · +4dCandidate
Illinois State AGbd_c3ee7acc686ad2c12025-08-01 · +21dVerified

Name: EventConnect
norm: eventconnect
Domain: eventconnect.io

Name: EventConnect
norm: eventconnect
Domain: eventconnect.io
Industry: Technologyllm

Discovered: May 30, 2025
Breach occurred: May 28, 2025 – Jun 2, 2025
Undetected for: 2 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jul 7, 2025
Affected individuals: Not disclosed
Data types: PIIIdentity (basic)Financial accountPCI
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Provided courtesy notice to New Hampshire Attorney General
Initial access: exploit_public_facing

During the incident: Took steps to secure the platform
Deployed additional security measures
Began working with external forensic specialists
Identified the threat and took our systems offline
Providing access to credit monitoring services for 24 months
Changes made: Deployed additional security measures to prevent similar attacks from occurring in the future
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Iowa State AGJul 7 · first

New Hampshire State AG+4d · this page

Illinois State AG+25d

Pattern: first filing Jul 7 (IA), last Aug 1 (IL) — a 25-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://mm.nh.gov/files/uploads/doj/remote-docs/eventconnect-20250711.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 11, 2025
Raw hash: 7bce8aec13804de0ca9c33cab47a361f1e3c0ae31f0654247f7233c0f48a9723

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityEventConnect

Victim entityEventConnect

Incidentdiscovered May 30, 2025

Stated responseTook steps to secure the platform

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov