Incident record
농촌진흥청·미소테크
Rural Development Administration & Misotech · Public
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
~575,000 records (includes duplicates)
Disclosure recorded
2026-05-27
Sector
Public
Practical risk
High
What this means
A practical reading of this record
The public record supports a high 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.
The reported figure includes duplicates. The incident is listed as a confirmed data breach based on the regulator decision and corroborating reporting.
Recorded source · PIPC 10th plenary decision 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
2026-05-27
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
Reported compromise
An unauthorised actor reportedly obtained entrusted public-sector data from a vendor NAS.
- 02
PIPC decision
PIPC imposed sanctions concerning the handling and exposure of the entrusted data.
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.