HackingProfessional ServicesProfessional ServicesStolen CredentialsTargetedPIILowContained

Form I-9 Compliance

bd_e493ce065e457e96 · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 12, 2024

Filed

May 31, 2024

To disclose

7 weeks

Affected

54state residents only

Linked

6 filings

Confidence

65%

Full breach record for Form I-9 Compliance →4 incidents on file

Form I-9 Compliance experienced unauthorized network access on or about February 5, 2024, discovered on April 12, 2024. The incident involved personal information of customers. The company engaged external experts, reset credentials, and reported to law enforcement. No fraud was identified at the time of notification.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 67 days

discovery → filing · 7 weeks / 49 days

Feb 5, 2024

Begins

Apr 12, 2024

Discovered

May 31, 2024

Filed

vs. sector median

12 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Maine State AGbd_401ba42cacddd1482024-05-31Verified
Massachusetts State AGbd_8f1b1107ccf28e192024-05-31Verified
California State AGbd_8f688b221999a8af2024-05-31Candidate
Indiana State AGbd_d920f5f5481dc1cd2024-05-31Verified

Show 1 more filing ↓up to 10d gap

New Hampshire State AGbd_18442bbc433502a52024-06-10 · +10dVerified

Name: Form I-9 Compliance
norm: form i 9 compliance

Name: Form I-9 Compliance
norm: form i 9 compliance
Industry: Professional Servicesllm

Discovered: Apr 12, 2024
Breach occurred: Feb 5, 2024
Undetected for: 67 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 54state-resident count only
Data types: PII
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: reported the incident to law enforcement
Initial access: valid_credentials

During the incident: Took a portion of our network offline
Activated our response process
Launched an investigation of the incident with the support of external cybersecurity experts
Reported the incident to law enforcement
Reset all account credentials associated with the affected portion of our network
Implemented additional security measures with the guidance of external experts
Changes made: Implemented additional security measures with the guidance of external experts to strengthen the ongoing security of our network
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Maine State AGMay 31 · first

Massachusetts State AGMay 31 · first

California State AGMay 31 · first

Indiana State AGMay 31 · first

Montana State AGMay 31 · first · this page

New Hampshire State AG+10d

Pattern: first filing May 31 (ME), last Jun 10 (NH) — a 10-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/OCP/Consumer-notification-letter-1443.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 31, 2024
Raw hash: 8e5ff62674b6e5f28ca4d76da93d5fbb1454205bc8313042797621cf4eeb9031

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityForm I-9 Compliance

Victim entityForm I-9 Compliance

Incidentdiscovered Apr 12, 2024

Stated responseTook a portion of our network offline

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov