Cyber & AI intelligence
Briefs indexed3800
Issues37
Published Mondays07:30 CT
▣ Breach NORAN-UMBRELLA-KBI 2026-11-18

Noran Umbrella (KBIZ): Website Intrusion Exposes Data of 205,000 to 362,000 Members

"An unauthorised outsider got into the website of Noran Umbrella (노란우산, also called Yellow Umbrella), the mutual aid fund for small businesses run by the Korea Federation of SMEs (KBIZ). Member records were viewed during…"

An unauthorised outsider got into the website of Noran Umbrella (노란우산, also called Yellow Umbrella), the mutual aid fund for small businesses run by the Korea Federation of SMEs (KBIZ). Member records were viewed during the intrusion. The number of people affected has grown fast. KBIZ's breach report to the Personal Information Protection Commission (PIPC), filed on November 14, said about 205,000 people's data showed signs of exposure. On November 18 Yonhap reported a higher figure from KBIZ, based on an outside forensic firm's investigation: 362,000 people. That is about 18.9% of the fund's 1.92 million members, or roughly one in five. Leaked fields include names, the first seven digits of resident registration numbers (RRNs), phone numbers, home and business addresses, business registration numbers and contribution amounts. The PIPC says it is looking into how the leak happened and how KBIZ handled notification and follow-up.

What Happened

KBIZ's report to the PIPC, as cited by Yonhap and SBS, gives this timeline:

A KBIZ official told Yonhap the organisation first estimated around 200,000 people and reported that number to KISA, then hired an outside firm separately to speed up the investigation. Early in the response, KBIZ said members who had not received a text were not among those suspected of exposure "based on findings so far" (Seoul Economic Daily). Since the count has now risen by about 160,000, that assurance may no longer hold. KBIZ has not said publicly whether the additional people have been notified.

A note on the 1.92 million figure: The Herald Business ran the headline "data breach affecting 1.92 million subscribers". That number is Noran Umbrella's total membership, not the number of people affected. No source, including KBIZ, says the whole membership was exposed.

What Was Taken

The first notice from November 14, reported the same way by Seoul Economic Daily, Chosunbiz, The Herald Business and JKN/Yonhap, listed seven categories:

Yonhap's November 18 report, based on the forensic findings, adds three more:

KBIZ says the last six digits of RRNs are stored with encryption that cannot be decrypted and were not exposed. It also says it does not collect bank account passwords, so nothing in the leak would let anyone withdraw money from accounts directly. Both statements come from KBIZ alone and have not been independently checked. KBIZ has also warned that the scope and the data fields involved could still change as the investigation goes on.

Accounts of the number of people differ by date and source. The figure ranges from about 205,000 (KBIZ's November 14 PIPC report, confirmed by the PIPC) to 362,000 (KBIZ's later figure from the forensic firm, reported by Yonhap). The higher figure is more recent, but the PIPC had not publicly confirmed it at the time of writing.

Why It Matters

This data makes very convincing scam material. Each record ties a person's name, date of birth, home address, phone numbers, business registration number and the amount they pay into a retirement-style fund. Fraudsters can use that to pose as KBIZ, a bank or a tax office and quote details that only the real organisation should know. KBIZ's own warnings point to the scams it expects: fake KBIZ or Noran Umbrella calls and texts offering loans or asking for money, and messages asking members to enter or change their ID and password.

The victims are small business owners. They often handle payments, invoices and supplier contacts themselves, without a finance team to catch a fake request. With business registration numbers and contribution amounts, an attacker can pose convincingly as a supplier, a lender or a government benefits office.

The number keeps rising. The affected count grew by about 75% between the first regulator filing and the forensic results. Early counts, made before outside forensics, tend to be too low. Anyone tracking Korean breaches should treat first figures as a minimum.

It fits a pattern of breaches in South Korea. Daily Briefing groups this case with a separate breach at Inje University in Gimhae, which says attackers took 24,011 student and staff records from a server used to run classes. Nothing indicates the two incidents are linked.

The Attack Technique

KBIZ has given few technical details. What it has said publicly:

Taken together, this is consistent with abuse of a web page or function that returned member records, for example a lookup page with weak authorisation or an insecure direct object reference (IDOR), or automated mass querying. That is our analysis, not something KBIZ has confirmed. KBIZ has not said whether attackers used stolen member credentials, exploited a vulnerability, or went through an exposed API. No group has claimed the attack, no leaked dataset has been publicly reported, and no ransom demand has been mentioned. KISA and the PIPC have not published technical findings.

What Organizations Should Do

  1. Check every page and API that returns personal data for authorisation flaws. Confirm that each request for a member record is checked against the logged-in user's own identity, not just against whether they are logged in. Test for IDOR by changing record IDs, and include these tests in regular penetration testing.
  2. Rate-limit and monitor record lookups. Set a baseline for how many lookups a single session or IP normally makes, and alert on volume, sequential ID walking or unusual times of day. KBIZ took about six and a half hours to notice this incident. Detection on the lookup function itself would cut that gap.
  3. Return only the fields a page needs. If a page shows a member's name, it should not also return their address, business registration number and contribution amount. Mask partial RRNs and other identifiers by default.
  4. Plan for the count to change. Bring in outside forensics early, tell regulators that first figures are provisional, and have a process ready to notify people added to the count later. Don't tell people they are safe until the full scope is known.
  5. Warn members about scams before they arrive. State plainly which channels you will never use to ask for money, loans or credentials, as KBIZ did, and publish an official number members can call to check. Financial institutions that serve the same small business customers should expect impersonation attempts quoting real KBIZ data.
  6. Affected members: treat any unexpected call or text that mentions your Noran Umbrella membership, contribution amount or business registration number as suspicious. Call KBIZ back on its published number. Change any password you reused on the Noran Umbrella site, and watch for loan or account applications made in your name.

Sources: Personal Info of Over 200,000 People Leaked from 'Noran Umbrella' | Korea Federation of SMEs' Noran Usan site hit by data breach affect... | Personal Data of Yellow Umbrella Members Possibly Leaked - Seoul Ec... | Names, phone numbers, and addresses exposed... Yellow Umbrella anno... | Recent Personal Data Breaches at Noran Umbrella and Inje University... | KBIZ reports possible Yellow Umbrella data leak, blocks IP and aler... | 노란우산 개인정보 유출 36만2천명 달해…당초보다 16만명 늘어(종합) 연합뉴스 | 노란우산 개인정보 유출 20만5천명 규모…가입자 10명 중 1명꼴 연합뉴스