UnknownMedium

Sarku Japan

bd_6f1f4c9b26bfab19 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 6, 2022

Filed

Mar 16, 2022

To disclose

5 weeks

Affected

28,298

Linked

10 filings

Confidence

95%

Full breach record for Sarku Japan →3 incidents on file

Sarku Japan reported a data breach to the Oregon Attorney General. The breach was reported on 2022-03-16. The breach occurred during 1/13/2022 - 2/6/2022. The breach was discovered on 2/6/2022. 28,298 individuals were affected. Notice was sent on 3/16/2022.

J jump to incidentP pin to compareR raw source

Oregon clock✓ OR AG ≤45d5 weeks 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 · 24 days

discovery → filing · 5 weeks / 38 days

Jan 13, 2022

Begins

Feb 6, 2022

Discovered

Mar 16, 2022

Filed

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

Linked disclosures

Why this link?

Regulatory filings (9) · sorted by filing gap

Washington State AGbd_154978068a8580a42022-03-16Candidate
Indiana State AGbd_3aca2a3d12cc197b2022-03-16Verified by operator
California State AGbd_3e7e01e462f64ab02022-03-16Verified
Massachusetts State AGbd_4842d37d019f458e2022-03-16Verified by operator

Show 5 more filings ↓up to 149d gap

Maine State AGbd_676946af941027ba2022-03-16Verified
New Hampshire State AGbd_82f05d9f8f47e5332022-03-21 · +5dVerified by operator
California State AGbd_2e9e3b153a51c8a62022-08-08 · +145dVerified
Maine State AGbd_e82af6a75bb3e3f12022-08-08 · +145dVerified
New Hampshire State AGbd_c728b2a05ad2d3562022-08-12 · +149dVerified by operator

Name: Sarku Japan
norm: sarku japan
Domain: sarkujapan.com

Name: Sarku Japan
norm: sarku japan
Domain: sarkujapan.com

Discovered: Feb 6, 2022
Breach occurred: Jan 13, 2022 – Feb 6, 2022
Undetected for: 24 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 16, 2022
Affected individuals: 28,298nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 5 weeks(38 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 · 10 filings · 7 states

View merged incident ↗

Washington State AGMar 16 · first

Indiana State AGMar 16 · first

California State AGMar 16 · first

Massachusetts State AGMar 16 · first

Maine State AGMar 16 · first

Oregon State AGMar 16 · first · this page

New Hampshire State AG+5d

California State AG+145d

Maine State AG+145d

New Hampshire State AG+149d

Pattern: first filing Mar 16 (WA), last Aug 12 (NH) — a 149-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: Mar 16, 2022
Raw hash: 935926cb852a4f0a175f38ebff503a1ef54ff19067afa5df0d89b41aa7161122

Linked disclosures

Regulatory filings (9) · sorted by filing gap

Reporting entitySarku Japan

Victim entitySarku Japan

Incidentdiscovered Feb 6, 2022

ComplianceOR AG ≤45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov