HackingRetail & ConsumerRetailCustomer Data InvolvedIdentity (basic)Financial accountLowContained

Made In Oregon

bd_7efe2ddfcbdd679b · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jun 18, 2021

To disclose

—

Affected

Not disclosed

Linked

7 filings

Confidence

64%

Full breach record for Made In Oregon →3 incidents on file

Naito Corporation dba Made In Oregon reported that between September 2020 and March 2021, an unauthorized party may have accessed personal information submitted via madeinoregon.com. Affected data includes names, billing/shipping addresses, email addresses, and credit card information. The company engaged forensic consultants, modified its website to stop accepting personal info, and is deploying a new secure website. Complimentary identity monitoring is offered.

J jump to incidentP pin to compareR raw source

Incident timeline

Sep 1, 2020

Begins

Jun 18, 2021

Filed

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Montana State AGbd_780ad110f3a857772021-06-16 · +2dCandidate
Indiana State AGbd_01d62431247fb74c2021-06-22 · +4dVerified
New Hampshire State AGbd_81dd9834f8db446b2021-06-22 · +4dVerified
Washington State AGbd_fb58f1d5247467d22021-06-22 · +4dVerified

Show 2 more filings ↓up to 33d gap

South Carolina State AGbd_ba30aa9f4043b8e62021-06-23 · +5dVerified
Oregon State AGbd_7d61036037d4cf672021-07-21 · +33dVerified

Name: Made In Oregon
norm: made in oregon
Domain: madeinoregon.com

Name: Made In Oregon
norm: made in oregon
Domain: madeinoregon.com
Also named: Naito Corporationdba oflegal entity
Made In Oregondba oftrade name
Industry: Retail & Consumerllm

Discovered: —
Breach occurred: Sep 1, 2020 – Mar 31, 2021
Materiality determined: —
Notification sent: Jan 1, 2021
Affected individuals: Not disclosed
Data types: Identity (basic)Financial account
Attack vector: Unknown
Threat actor: External
Regulator citations: Working with law enforcement to ensure the incident is properly addressed

During the incident: Working with consultants in computer forensics
Conducting a thorough review of the potentially affected data
Modified our website so that it no longer accepts any personal information
Deploying a completely new website using different software running at a new website hosting company
Deploying tight security on the website
Working with law enforcement to ensure the incident is properly addressed
Offering complimentary access to Experian Identity Works for two years
Changes made: Deploying a completely new website using different software running at a new website hosting company
Deploying tight security on the website
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Montana State AGJun 16 · first

California State AG+2d · this page

Indiana State AG+6d

New Hampshire State AG+6d

Washington State AG+6d

South Carolina State AG+7d

Oregon State AG+35d

Pattern: first filing Jun 16 (MT), last Jul 21 (OR) — a 35-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://oag.ca.gov/ecrime/databreach/reports/sb24-542062
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 18, 2021
Raw hash: 2e87ca1ad966d9ee527de8633800802a79d16152cc889c14bc6550cf71a9975c

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityMade In Oregon

Victim entityMade In Oregon

IncidentUnknown

Stated responseWorking with consultants in computer forensics

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov