HackingRetail & ConsumerRetailVulnerability ExploitTargetedData ExfiltratedIdentity (basic)Financial accountLowContained

AKIRA

bd_cb93e9717f4fc99b · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 18, 2017

Filed

Sep 1, 2017

To disclose

6 weeks

Affected

12state residents only

Linked

4 filings

Confidence

63%

Full breach record for AKIRA →

Akira (shopakira.com) notified customers of a data breach involving unauthorized access to payment card information and PII from November 2016 to July 2017. Malicious code collected checkout data. Forensic investigators confirmed the infection on July 18, 2017. Code was removed and additional security measures implemented. Notices sent September 1, 2017.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 259 days

discovery → filing · 6 weeks / 45 days

Nov 1, 2016

Begins

Jul 18, 2017

Discovered

Sep 1, 2017

Filed

vs. sector median

3 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

New Hampshire State AGbd_05392b94426154142017-09-01Verified
Massachusetts State AGbd_2bd90a4e783ba46e2017-09-01Verified
California State AGbd_43f1d8311789a6542017-09-01Verified

Name: AKIRA
norm: akira
Domain: shopakira.com

Name: AKIRA
norm: akira
Domain: shopakira.com
Industry: Retail & Consumerllm

Discovered: Jul 18, 2017
Breach occurred: Nov 1, 2016 – Jul 1, 2017
Undetected for: 259 daysoccurrence → discovery
Materiality determined: —
Notification sent: Sep 1, 2017
Affected individuals: 12state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: notify any required state regulatorsnotify the credit reporting agencies
Initial access: exploit_public_facing

During the incident: Launched an internal investigation
Hired a third party forensic investigator
Removed the infected code from our website
Implemented additional security measures
Changes made: Removed the infected code that led to the vulnerability
Implemented additional security measures to reduce the likelihood of a similar incident from happening in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 6 weeks(45 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 AGSep 1 · first

Massachusetts State AGSep 1 · first

California State AGSep 1 · first

Montana State AGSep 1 · 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://dojmt.gov/wp-content/uploads/Akira.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 1, 2017
Raw hash: 807150d7d96ca12b9fb65359733b6b755a9a5152c5f560f4cc123655331a90e1

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityAKIRA

Victim entityAKIRA

Incidentdiscovered Jul 18, 2017

Stated responseLaunched an internal investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov