HackingTechnologyInformationVulnerability ExploitCustomer Data InvolvedDelayed DiscoveryIdentity (basic)CredentialsFinancial accountFinancial credentialsLowContained

Zymo Research Corporation

bd_7273bdbd187833b6 · schema v1 · pii pii-v1

Severity

Low

Discovered

Aug 2, 2017

Filed

Aug 25, 2017

To disclose

23 days

Affected

Not disclosed

Linked

4 filings

Confidence

65%

Full breach record for Zymo Research Corporation →

Zymo Research Corporation discovered on August 2, 2017, that its external cloud e-commerce network was accessed by an unknown actor on March 15, 2017. The attacker placed code on the system to access a customer database containing names, addresses, emails, hashed passwords, and credit card information (numbers, CVVs, expiration dates). Zymo retained a third-party forensic firm, implemented additional security measures, and offered one year of identity monitoring via Kroll. The incident affected customers in California and Wyoming.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 140 days

discovery → filing · 23 days

Mar 15, 2017

Begins

Aug 2, 2017

Discovered

Aug 25, 2017

Filed

vs. sector median

8 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Massachusetts State AGbd_1dafbe148f2cf8382017-08-23 · +2dVerified
Montana State AGbd_f5d0519e31eb3e792017-08-28 · +3dVerified
New Hampshire State AGbd_8d6f2dc0d35e7adc2017-08-21 · +4dVerified

Name: Zymo Research Corporation
norm: zymo research
Domain: zymoresearch.com

Name: Zymo Research Corporation
norm: zymo research
Domain: zymoresearch.com
Industry: Technologyllm

Discovered: Aug 2, 2017
Breach occurred: Mar 15, 2017
Undetected for: 140 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)CredentialsFinancial accountFinancial credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Initial access: exploit_public_facing

During the incident: Conducting a thorough review of the potentially affected computer systems
Retained a third-party firm to conduct a forensic investigation
Implemented additional security measures designed to prevent the recurrence of such an attack
Secured the services of Kroll to provide identity monitoring at no cost for one year
Changes made: Implemented additional security measures designed to prevent the recurrence of such an attack
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

New Hampshire State AGAug 21 · first

Massachusetts State AG+2d

California State AG+4d · this page

Montana State AG+7d

Pattern: first filing Aug 21 (NH), last Aug 28 (MT) — a 7-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-101370
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 25, 2017
Raw hash: 1e38aaaa6a13576e309ab00ff14c885099a043e3a2a2a38bb15b7c11a6b62bee

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityZymo Research Corporation

Victim entityZymo Research Corporation

Incidentdiscovered Aug 2, 2017

Stated responseConducting a thorough review of the potentially affected computer systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov