MalwareRetail & ConsumerRetailData ExfiltratedTargetedPCIFinancial accountIdentity (basic)LowContained

Manduka

bd_3e061c3e758c0dce · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 25, 2018

Filed

Mar 27, 2018

To disclose

4 weeks

Affected

279state residents only

Linked

7 filings

Confidence

66%

Full breach record for Manduka →3 incidents on file

Manduka notified the NH Attorney General of a data security incident discovered on Feb 25, 2018. Malware was installed on its e-commerce platform, affecting payment card info (names, numbers, expiration, CVV) of customers who purchased between Feb 22, 2017 and Mar 5, 2018. 279 NH residents were notified. Manduka engaged forensics, notified the FBI, and secured the platform.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 368 days

discovery → filing · 4 weeks / 30 days

Feb 22, 2017

Begins

Feb 25, 2018

Discovered

Mar 27, 2018

Filed

vs. sector median

3 wks faster

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

Washington State AGbd_459f89eec19797642018-03-27Verified
Oregon State AGbd_5ecb4e4d561a06bf2018-03-27Verified
California State AGbd_7ff02f57c56732092018-03-27Verified
Montana State AGbd_900e824b2ddbde8d2018-03-26 · +1dCandidate

Show 2 more filings ↓up to 127d gap

California State AGbd_197f9054f6cba4652018-06-08 · +73dVerified
New Hampshire State AGbd_7e59e035c09ab18b2018-08-01 · +127dVerified

Name: Manduka
norm: manduka

Name: Manduka
norm: manduka
Industry: Retail & Consumerllm

Discovered: Feb 25, 2018
Breach occurred: Feb 22, 2017 – Mar 5, 2018
Undetected for: 368 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 26, 2018
Affected individuals: 279state-resident count only
Data types: PCIFinancial accountIdentity (basic)
Attack vector: Unknown
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Notified New Hampshire Attorney GeneralNotified Federal Bureau of Investigation
Initial access: exploit_public_facing

During the incident: Contacted the appropriate law enforcement agencies including the Federal Bureau of Investigation
Launched an investigation and engaged a leading forensics firm
Reported the matter to the payment card brands
Working with a leading forensics firm to remove malicious code from its e-commerce web platform
Blocked traffic to / from malicious domains
Secured its e-commerce platform (Magento)
Reduced administrative access to its e-commerce platform
Changed all user and administrative passwords
Changes made: Removed malicious code from its e-commerce web platform
Blocked traffic to / from malicious domains
Secured its e-commerce platform (Magento)
Reduced administrative access to its e-commerce platform
Changed all user and administrative passwords
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 5 states

View merged incident ↗

Montana State AGMar 26 · first

Washington State AG+1d

Oregon State AG+1d

California State AG+1d

New Hampshire State AG+1d · this page

California State AG+74d

New Hampshire State AG+128d

Pattern: first filing Mar 26 (MT), last Aug 1 (NH) — a 128-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://mm.nh.gov/files/uploads/doj/remote-docs/manduka-20180327.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 27, 2018
Raw hash: 44efeca3b0981e94de5399d9d597ae07ab0da3dd50015ab0b958e92e9f06a090

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityManduka

Victim entityManduka

Incidentdiscovered Feb 25, 2018

Stated responseContacted the appropriate law enforcement agencies including the Federal Bureau of Investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov