HackingRetail & ConsumerRetailCustomer Data InvolvedPIIIdentity (basic)Financial accountCredentialsLowContained

Oiselle Running Inc.

bd_0263129d3f0a5e82 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 5, 2015

Filed

Jan 29, 2016

To disclose

12 weeks

Affected

5state residents only

Linked

3 filings

Confidence

66%

Full breach record for Oiselle Running Inc. →

Oiselle Running Inc. disclosed that criminal hacking activity on its website, oiselle.com, between Oct 29 and Nov 5, 2015, exposed customer transaction data including names, emails, billing addresses, credit card numbers, and CVV codes. The company notified affected customers and engaged the FBI.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 7 days

discovery → filing · 12 weeks / 85 days

Oct 29, 2015

Begins

Nov 5, 2015

Discovered

Jan 29, 2016

Filed

vs. sector median

+5 wks slower

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

New Hampshire State AGbd_38bdb81a4ab57d902016-01-29Verified
Massachusetts State AGbd_36a739964e16f3512016-02-02 · +4dVerified

Name: Oiselle Running Inc.
norm: oiselle running
Domain: oiselle.com

Name: Oiselle Running Inc.
norm: oiselle running
Domain: oiselle.com
Industry: Retail & Consumerllm

Discovered: Nov 5, 2015
Breach occurred: Oct 29, 2015 – Nov 5, 2015
Undetected for: 7 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 5state-resident count only
Data types: PIIIdentity (basic)Financial accountCredentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Contacted law enforcement officials at the Federal Bureau of Investigations
Initial access: exploit_public_facing

During the incident: Contacted law enforcement officials at the Federal Bureau of Investigations
Cooperating fully with the investigation
Implemented enhanced security measures
Changes made: Implemented enhanced security measures designed to prevent a recurrence of this type of incident
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

New Hampshire State AGJan 29 · first

Montana State AGJan 29 · first · this page

Massachusetts State AG+4d

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/Oiselle.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 29, 2016
Raw hash: a1e6c65fb15156fccaa7753290fbb62618dda53cfef78abaffc06d6673aa34f4

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityOiselle Running Inc.

Victim entityOiselle Running Inc.

Incidentdiscovered Nov 5, 2015

Stated responseContacted law enforcement officials at the Federal Bureau of Investigations

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov