HackingHospitalityHospitalitySkimmerData ExfiltratedCustomer Data InvolvedDelayed DiscoveryFinancial accountIdentity (basic)PIILowContained

Landry's, Inc.

bd_06e1647b0be8d4e0 · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 3, 2015

Filed

Jan 29, 2016

To disclose

8 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

70%

Full breach record for Landry's, Inc. →3 incidents on file

Landry's, Inc. disclosed a payment card skimming incident affecting multiple restaurant and hospitality locations. Attackers installed malware on payment processing devices to capture magnetic stripe data (card numbers, names, CVVs) from May 2014 to December 2015. The breach was discovered in December 2015. No specific count of affected individuals was provided; substitute notification was issued via website and press release.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 578 days

discovery → filing · 8 weeks / 57 days

May 4, 2014

Begins

Dec 3, 2015

Discovered

Jan 29, 2016

Filed

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

Oregon State AGbd_3c2ab6f22eb45e4a2016-01-29Verified
California State AGbd_7d926ef7ed7260042016-01-29Verified

Name: Landry's, Inc.
norm: landry s

Name: Landry's, Inc.
norm: landry s
Industry: Hospitalityllm

Discovered: Dec 3, 2015
Breach occurred: May 4, 2014 – Dec 3, 2015
Undetected for: 578 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 29, 2016
Affected individuals: Not disclosed
Data types: PIIFinancial account
Data elements: Financial account numberName
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 500+dexposure 500+d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Unauthorized Access
MITRE ATT&CK: T1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Regulator citations: Notified Attorney General Bob Ferguson
Initial access: external_remote_services

During the incident: Hired a leading cyber security firm to examine their payment card system
Contacted the payment card networks and law enforcement about the incident
Established a dedicated call center that potentially affected individuals can contact with questions
Working closely with the payment card networks to identify potentially affected cards so that the card issuers can be made aware and initiate heightened monitoring of those accounts
Changes made: Implemented enhanced security measures, including end-to-end encryption, to prevent a similar issue from occurring in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 weeks(57 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 ↗

Oregon State AGJan 29 · first

California State AGJan 29 · first

Washington State AGJan 29 · first · this page

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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9608.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: 01ecbfa03841afb94d9615314ac7d2f6f0fa732d3cff5e520c77afdb3e2a1dc4

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityLandry's, Inc.

Victim entityLandry's, Inc.

Incidentdiscovered Dec 3, 2015

Stated responseHired a leading cyber security firm to examine their payment card system

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com