HackingRetail & ConsumerRetailStolen CredentialsTargetedData ExfiltratedIdentity (basic)Financial accountLowContained

Etz Hayim Holdings, SPC. d/b/a Lazarus Naturals

bd_b49e3b5a7df8341b · schema v1 · pii pii-v1

Severity

Low

Discovered

Sep 14, 2020

Filed

Nov 30, 2020

To disclose

11 weeks

Affected

31state residents only

Linked

5 filings

Confidence

66%

Etz Hayim Holdings d/b/a Lazarus Naturals disclosed a data breach occurring between September 5 and 14, 2020, where malicious code on the checkout page captured customer names, addresses, and payment card details. The company engaged forensic investigators, removed the code, and migrated to a new platform. Credit monitoring was offered.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 9 days

discovery → filing · 11 weeks / 77 days

Sep 5, 2020

Begins

Sep 14, 2020

Discovered

Nov 30, 2020

Filed

vs. sector median

+3 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Oregon State AGbd_463c8204d5747ff52020-11-30Candidate
Maine State AGbd_72e3fb110935c9972020-11-30Verified
California State AGbd_c0da585491bdcca22020-11-30Verified
New Hampshire State AGbd_df4e29291edc85b52020-12-11 · +11dVerified

Name: Etz Hayim Holdings, SPC. d/b/a Lazarus Naturals
norm: etz hayim holdings

Name: Etz Hayim Holdings, SPC. d/b/a Lazarus Naturals
norm: etz hayim holdings
Also named: Etz Hayim Holdings, SPC.dba oflegal entity
Lazarus Naturalsdba oftrade name
Industry: Retail & Consumerllm

Discovered: Sep 14, 2020
Breach occurred: Sep 5, 2020 – Sep 14, 2020
Undetected for: 9 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 31state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Immediately removed the malicious code and conducted a thorough internal investigation of what happened, how it happened, and how to prevent it in the future
Engaged a third-party forensic investigation team to review our internal processes, systems, and other relevant information, who confirmed we took the proper steps to protect our customers
Enacted new security protocols and restructured our server architecture to remove the possibility of a similar situation in the future
Notified potentially impacted customers of the incident via this letter with ways you can protect your personal information
Implemented a planned migration from our previous website platform on which this incident occurred, to a new, more secure, platform
Changes made: Enacted new security protocols and restructured our server architecture to remove the possibility of a similar situation in the future
Implemented a planned migration from our previous website platform on which this incident occurred, to a new, more secure, platform
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Oregon State AGNov 30 · first

Maine State AGNov 30 · first

California State AGNov 30 · first

Montana State AGNov 30 · first · this page

New Hampshire State AG+11d

Pattern: first filing Nov 30 (OR), last Dec 11 (NH) — a 11-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://dojmt.gov/wp-content/uploads/etzSamp.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 30, 2020
Raw hash: ebc9933f570bd1bbd2567d846588f6d124974ec700a814a0c5e397842a64b1fb

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityEtz Hayim Holdings, SPC. d/b/a Lazarus Naturals

Victim entityEtz Hayim Holdings, SPC. d/b/a Lazarus Naturals

Incidentdiscovered Sep 14, 2020

Stated responseImmediately removed the malicious code and conducted a thorough internal investigation of what happened, how it happened, and how to prevent it in the future

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov