Security Guides

Rumoi City Resident Data (Up to 71,002 Records) and Support-Needed Data (Up to 4,503) May Have Leaked: A Contractor's Subcontractor Device Was Infected With Malware. What Affected People Should Do

Rumoi City, Japan says a subcontractor's device holding data from a GIS project was infected with malware. Up to 71,002 resident records may have leaked.

Published 2026-11-21 Updated 2026-11-21 Last verified 2026-11-21 8 min read
On this page

For: people who were on Rumoi City's resident register as of February 3, 2022, or registered as needing support in March 2022, and their families; and organisations that outsource local-government work. This article is based on Rumoi City's official notice and does not cover attack techniques.

Developing: this article will be updated as the organisation publishes more

Who is affected

people who were on Rumoi City's resident register as of February 3, 2022, or registered as needing support in March 2022, and their families; and organisations that outsource local-government work.

Confirmed so farSee the table ↓
  • Device infection

Listed as possibly affected

  • Resident register data
  • Support-needed data
Not yet confirmed
  • Whether anything actually left the device, and the scope of impact
  • Infection route, and why the data remained on the device after the contract ended
  • Whether affected people will be notified individually
1 more
  • Recurrence prevention measures
What to do nowSee the steps ↓
  1. Check whether you may be affected
  2. Do not respond on the spot to contact in the name of the city or welfare staff
  3. If you are registered as needing support, share the caution with family and supporters
1 more
  1. Ask the city office if you are worried
Last checked
As of November 21, 2026
Follow-up plans and what we checked

The city says the scope of impact and whether anything leaked are under investigation, and that it will announce new information again as it becomes known.

What people who may be affected should do today

1

Check whether you may be affected

Per the city's notice, the data that may have leaked is resident register data as of February 3, 2022 (up to 71,002 records) and data on people needing support as of March 2022 (up to 4,503 records).

If you were registered as a resident of Rumoi City at that time, you may be included in the former, even if you have moved out since. If you were registered as needing support, you may also be included in the latter. The notice does not say whether people will be told individually.

2

Do not respond on the spot to contact in the name of the city or welfare staff

The city urges people to be careful about suspicious contact. With name, address and date of birth together, convincing contact can be written.

If the talk turns to money or accounts, such as "you have a refund", "a procedure is needed" or "we need to check your account", do not respond; hang up. When you call back, use a number you looked up yourself, such as on the city's official website, not the number that called you (how to tell: What is phishing?).

3

If you are registered as needing support, share the caution with family and supporters

The support data may include items such as disability category and care-need level. Because the person may find phone calls hard, tell family and supporters too: do not answer on the spot when the city or welfare staff are named; check with the city office.

4

Ask the city office if you are worried

The contact named in the notice is the General Affairs Division (2nd floor, main city hall). The General Affairs staff line is 0164-42-1801; the other numbers are on the city's notice page. The city's site gives opening hours of 8:50 to 17:20 on weekdays.

What happened (from Rumoi City's notice)

The following is based on the notice of Rumoi City dated November 19, 2026.

  1. August 2020

    The city contracted a company for the "integrated GIS introduction project" (per the city's notice).
  2. Night of Nov 2 to Nov 3, 2026

    A development device of the contractor's subcontractor was infected with malware (per the city's notice).
  3. Nov 4

    The subcontractor found traces of infection and physically cut the device off from the network.
  4. Nov 13

    The contractor reported to the city by phone that a leak was possible and under investigation.
  5. Nov 14

    The city received the contractor's first written report.
  6. Nov 16

    The contractor explained the first report to the city.
  7. Nov 19

    The city posted its notice dated November 19. It says it is still collecting details and investigating.
Up to 71,002
Resident register records (as of Feb 3, 2022)
Up to 4,503
Support-needed records (as of Mar 2022)
Not included
My Number (individual number)
Not confirmed
Leak or misuse (as of the city's notice)
Data that may have leaked (from Rumoi City's notice)
Resident register data (as of Feb 3, 2022, up to 71,002 records)
System ID, household number, head of household name, name, name in kana, postal code, current address, gender, date of birth, previous address, head of household and address before change, address before moving in, destination address on moving out, actual residence address, filing dates and more (the notice says "and more")
Support-needed data (as of Mar 2022, up to 4,503 records)
System ID, disability category, main disability, physical, intellectual and mental disability, care-need level, name, name in kana, gender, age, date of birth, postal code, address, consent or non-consent to information sharing
Data not included
My Number (individual number). The city says it is in neither data set
Action taken
Physically cutting the infected device off the network (Nov 4). Collecting details and investigating

What is known and what is not

Status as of November 21, 2026. We will rewrite the status column as updates appear.

ItemWhat the notice saysStatus
Resident register dataAs of Feb 3, 2022, up to 71,002 records, including name, address, date of birthPossible (city)
Support-needed dataAs of Mar 2022, up to 4,503 records, including disability category and care-need levelPossible (city)
My NumberNot includedNot included (city)
Leak or misuseNot confirmed at this timeNot confirmed (city)
Device infectionTraces of infection with information-stealing malware on a subcontractor's development device; infected Nov 2 night to Nov 3, cut off Nov 4Confirmed (city's notice, based on the contractor's report)
Scope of impact and whether anything left the deviceUnder investigationUnder investigation
Infection routeNot mentioned in the noticeNot stated
Why data remained on the device after the contract endedNot mentioned (only that it remained)Not stated
Individual notices to affected peopleNot mentioned in the noticeNot stated

How to read this: 'risk' does not mean 'leaked', but it does not mean 'safe' either

The city says no leak or misuse has been confirmed. It also says data remained on a device showing traces of infection with information-stealing malware, so a leak is possible. The scope of impact and whether anything left the device are under investigation.

What name, address, date of birth, disability category and care-need level can enable

In general, name, address, date of birth and household information together let someone write convincing calls or letters in the name of a government office, bank or welfare service. Support-needed data covers disability category and care-need level, which call for particular care. That does not mean this data has been misused.

The data dates from 2022, so a current address may differ for people who have moved since.

For local governments and others who outsource work: what the published facts suggest

According to the notice, the infected device belonged not to the contractor but to its subcontractor, and personal data was still stored on it after the contract ended.

From the published timeline, these points follow:

  • Decide how return or deletion of personal data after a contract ends is confirmed, rather than assuming it
  • Extend the same rules to subcontractors by contract, and set a deadline and a contact for reporting incidents
  • Avoid using real resident data for development and testing (if it is used, fix the scope and period and delete it)

The infection route and why the data remained have not been disclosed, so this section does not assess the response of the city or the contractors.

Sources (public record)

The facts in this article come from the public information below. We have not speculated about any undisclosed route or technique.

  • Rumoi City, "About the risk of leakage of personal information" (Japanese title: 個人情報漏えいのおそれについて), dated November 19, 2026 — e-rumoi.jp

Update history

2026-11-21: First version, based on the city's notice dated November 19. The city says it will announce new information as it becomes known, and we will update this article when it does.

Latest breaking reports

All breaking reports →

FAQ

QWhat may have leaked in the Rumoi City incident?
A

According to Rumoi City, the data that may have leaked is resident register data as of February 3, 2022 (up to 71,002 records) and data on people needing support as of March 2022 (up to 4,503 records). The resident data includes items such as name, address, date of birth and gender; the support data includes items such as disability category and care-need level. The city says My Number is not included in either.

QAm I affected?
A

The city's notice covers resident register data as of February 3, 2022 and support-needed data as of March 2022. People who were on Rumoi City's resident register at that time, or registered as needing support, may be included. The notice says nothing about individual notices. If you are worried, ask the General Affairs Division named in the notice.

QDid the data actually leak?
A

As of the notice dated November 19, 2026, the city says no leak or misuse has been confirmed. It is a risk of leakage, and the scope of impact and whether anything left the device are under investigation.

QWas My Number leaked?
A

According to the city's notice, My Number (the individual number) is not included in either of the two data sets that may have leaked.

QWhat caused it?
A

The city says traces of infection with information-stealing malware were found on a development device of the subcontractor of the company it contracted for a GIS project. The device was infected between the night of November 2 and November 3, and the subcontractor found the traces on November 4 and physically cut it off from the network. How the data came to remain on the device after the contract ended, and how it was infected, have not been disclosed.

QWhat if someone contacts me claiming to be the city?
A

The city urges people to be careful about suspicious contact. If a call, email or visit in the name of the city or welfare staff raises bank account numbers, PINs or money, do not respond on the spot; phone the city office using a number you looked up yourself.