Incident record

비지에프네트웍스 (CU POST)

BGF Networks (CU POST) · Retail

Confirmed

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

Not disclosed

Disclosure recorded

2026-06-05

Sector

Retail

Practical risk

Critical

What this means

A practical reading of this record

The public record supports a critical practical risk level based on the currently reported scope and data categories. This can change if the organisation or regulator updates the record.

  • Change the password for this service through its official app or website. Change it anywhere you reused it.
  • Expect targeted phishing and account-recovery scams. Do not share verification codes with an unsolicited caller.

Classification

Data breach

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 company did not publicly disclose an affected-member total. Information entered for parcel recipients was reported as outside the affected scope.

Recorded source · BGF Networks 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

2026-06-05

The most recent dated event currently documented on this page.

  1. Confirmed

    Current status recorded from the first documented public event in this entry.

Documented events

Public timeline

2 milestones1 days documented
  1. 01

    Unauthorised access identified

    BGF Networks said an unidentified attacker accessed its system without authorisation.

  2. 02

    Customer notice

    CU POST published a notice and reported the incident to PIPC and KISA.

Data reported exposed

Account IDPassword (hashed)NameDate of birthGenderAddressEmailPhone numberConnected information (CI)

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.

Secure your account

Correction

Is something inaccurate or outdated?

Send a public source or official correction. Material updates are logged rather than silently replacing the record.

Report an error