Incident record
신세계아이앤씨
Shinsegae I&C · Retail
This record separates what has been publicly claimed, investigated, and confirmed. It does not imply that every affected account belongs to a unique person.
Reported impact
~80,000 employee and partner records
Disclosure recorded
2025-12-26
Sector
Retail
Practical risk
Low
What this means
A practical reading of this record
The public record supports a low practical risk level based on the currently reported scope and data categories. This can change if the organisation or regulator updates the record.
- Follow the organisation’s official notice, use a unique password, and be cautious of follow-up messages using details from the incident.
Classification
Categories are assigned only where the currently stored public record supports them. A privacy decision is not automatically treated as a hacking incident.
Evidence status
Why it appears in the index
Confirmed by the organisation, a regulator, or a documented official decision.
Reporting describes employee and partner data, not customer data. The exact origin and full scope were still being investigated.
Recorded source · Shinsegae I&C disclosure and Korean media reporting
Direct source links are being standardised in the source archive. Until then, this page names the current evidence basis rather than substituting a generic link.
Editorial record
Review and status trail
Last reviewed
2026-09-21
The latest editorial review of the stored public record.
Latest source event
2025-12-26
The most recent dated event currently documented on this page.
Confirmed
Current status recorded from the first documented public event in this entry.
Documented events
Public timeline
- 01
Incident detected
The company identified an intrusion involving its internal network.
- 02
Public disclosure
The company publicly disclosed an incident involving employee and partner information.
Data reported exposed
Protect your account
Change your password if you use this service
Use a new, unique password through the official app or website. Change any other account where you reused it, and enable a passkey or two-factor authentication when available.
Correction
Is something inaccurate or outdated?
Send a public source or official correction. Material updates are logged rather than silently replacing the record.