UnknownFinanceHigh

Hatch Bank

bd_dbb2e668d0b81195 · schema v1 · pii pii-v1

Severity

High

Discovered

Feb 7, 2023

Filed

Feb 28, 2023

To disclose

21 days

Affected

139,493

Linked

7 filings

Confidence

95%

Full breach record for Hatch Bank →3 incidents on file

Hatch Bank reported a data breach to the Oregon Attorney General. The breach was reported on 2023-02-28. The breach occurred during 1/30/2023 - 1/31/2023. The breach was discovered on 2/7/2023. 139,493 individuals were affected. Notice was sent on 2/28/2023.

J jump to incidentP pin to compareR raw source

Oregon clock✓ OR AG ≤45d21 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 8 days

discovery → filing · 21 days

Jan 30, 2023

Begins

Feb 7, 2023

Discovered

Feb 28, 2023

Filed

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

Part of FORTRA, LLC supply-chain incident (2023) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Indiana State AGbd_05428a1fd24d3f9c2023-02-28Verified
Washington State AGbd_6a0fbcf8d7c0d53a2023-02-28Candidate
Vermont State AGbd_7138750bbfb556dc2023-02-28Verified
California State AGbd_9dbaa312cfff98b42023-02-28Verified

Show 2 more filings ↓up to 6d gap

Montana State AGbd_f5981ae8f8ed80132023-02-28Verified
New Hampshire State AGbd_30fc3880baa08a9e2023-03-06 · +6dVerified

Name: Hatch
norm: hatch
Domain: hatch.com

Name: Hatch Bank
norm: hatch bank

Discovered: Feb 7, 2023
Breach occurred: Jan 30, 2023 – Jan 31, 2023
Undetected for: 8 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 28, 2023
Affected individuals: 139,493nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 21 days(21 days from discovery to filing)
Compliance flags: OR AG ≤45d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Indiana State AGFeb 28 · first

Washington State AGFeb 28 · first

Vermont State AGFeb 28 · first

California State AGFeb 28 · first

Montana State AGFeb 28 · first

Oregon State AGFeb 28 · first · this page

New Hampshire State AG+6d

Pattern: first filing Feb 28 (IN), last Mar 6 (NH) — a 6-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://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 28, 2023
Raw hash: 5885462858580caee5106e05c02c36e3f0d4b509dd41e3f0b1a75b8791e4f4f7

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityHatch

Victim entityHatch Bank

Incidentdiscovered Feb 7, 2023

ComplianceOR AG ≤45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov