HackingHealthcareHealthcareCustomer Data InvolvedIdentity (basic)Government IDMediumContained

Avpro

bd_42b9257ea5c836a1 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 8, 2025

Filed

Apr 10, 2025

To disclose

5 weeks

Affected · nationwide

715 in this filing

Linked

3 filings

Confidence

66%

Full breach record for Avpro →2 incidents on file

Avpro, Inc. reported a cybersecurity incident on March 8, 2025, where an unauthorized third party hacked into its IT systems. The breach affected 71 individuals, including 5 Maine residents. Compromised data included names, addresses, and Social Security numbers. Avpro took the affected server offline, migrated infrastructure to Microsoft cloud, and offered 24 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Mar 8, 2025 → Filed with AG Apr 10, 202533d ⏱ ME AG >30d5 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 5 weeks / 33 days

Mar 8, 2025

Begins

Mar 8, 2025

Discovered

Apr 10, 2025

Filed

vs. sector median

6 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

Maine State AGbd_2084d21fa73c52612025-04-10Candidate
New Hampshire State AGbd_29288e168c9ac3b12025-04-10Verified

Name: Avpro
norm: avpro

Name: Avpro
norm: avpro
Industry: Healthcarellm

Discovered: Mar 8, 2025
Breach occurred: Mar 8, 2025
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 10, 2025
Affected individuals: 71state + nationwide
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: External
Initial access: exploit_public_facing

During the incident: Disabled and took offline the affected server device
Began an investigation
Conducted a review of the files that were accessed
Offering a complimentary, 24-month credit monitoring service with IDX
Changes made: Moving IT infrastructure to the Microsoft cloud platform
Implementing multi-factor identity and access management system
Implementing data encryption to protect against cyber threats
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(33 days from discovery to filing)
Compliance flags: ME AG >30d · 33d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Mar 8, 2025
→ Filed with AG: Apr 10, 2025
33d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Mar 8, 2025 → Filed with AG: Apr 10, 2025	33d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

Maine State AGApr 10 · first

New Hampshire State AGApr 10 · first

Maine State AGApr 10 · first · 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://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/6535daa6-2254-4f6d-b594-2793345cb5c5.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 10, 2025
Raw hash: 22fc3c772f006f357a7efe80f75ffc12ce0bd54d743a27b13bcf25453a8a5971

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityAvpro

Victim entityAvpro

Incidentdiscovered Mar 8, 2025

Stated responseDisabled and took offline the affected server device

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov