City of McMinnville Data Breach: What Happened and What You Should Do
City of McMinnville disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.
- Company
- City of McMinnville
- People affected
- Undisclosed
Vermont AG table lists 7 Vermont residents; Rhode Island addendum in the CA sample states 8 Rhode Island individuals. National headcount not stated.
- Incident date
- June 1 – July 18, 2026
- Discovered
- On or about July 15, 2026
- Disclosed
- September 29, 2026
- Information exposed
- Possibly: Name, Social Security number, Government identification
- Status
- Notification / monitoring offer underway
California AG sample reported September 29, 2026; Cyberscout monitoring for twelve months.
What happened in the City of McMinnville breach?
How the attacker got in
Unauthorized access and copying of certain information from the city's network between June 1 and July 18, 2026 (unusual activity noticed on or about July 15, 2026).
Reports conflict
Timeline of what is known
- 01June 1 – July 18, 2026Unauthorized access
- 02On or about July 15, 2026Breach discovered
- 03September 29, 2026Breach disclosed publicly
- 04September 29, 2026Affected individuals notified
Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.
What information was exposed?
The categories below come from City of McMinnville's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.
Name
Personal information may be impacted (company sample notice).
Social Security number
Social Security Numbers listed on Vermont AG Security Breach Notices table (September 29, 2026).
Government identification
Government ID Numbers listed on Vermont AG table.
Why this information matters
The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.
Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.
Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.
If you were affected, consider doing these things now
Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.
- 01Enroll in Cyberscout credit monitoring within 90 days at https://bfs.cyberscout.com/activate using the unique code in your letter.
- 02Call 1-833-544-7562 (Monday–Friday, 8:00 a.m.–8:00 p.m. Eastern) with questions.
- 03Review credit reports and account statements for activity you do not recognize.
- 04Consider a fraud alert or credit freeze with Equifax, Experian, and TransUnion.
- 05Watch for phishing that references the City of McMinnville, Cyberscout, or TransUnion.
AI Protection
Monitoring, removal, and recovery help for what comes after a breach.
A breach puts information you can't take back into circulation. AI Protection watches for it being misused, reduces what else can be found about you, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.
How one breach can contribute to a larger exposure footprint
A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.
Illustrative pattern- Step 1
One breach
A single company's records are accessed without authorization.
- Step 2
Personal information is exposed
Some categories can be changed afterward. Others, like a name or date of birth, can't.
- Step 3
It may remain accessible
Copies of breached data can persist well beyond the original incident.
- Step 4
Sources can be combined
Fragments from different breaches and public sources may be assembled into a fuller profile.
- Step 5
More targeted attempts
A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.
A breach is an event. Exposure can last longer.
A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.
Involved in this breach and hard to change
None of the categories reported in this breach are in the hard-to-change group. Changeable items like passwords and account numbers should still be addressed.
What City of McMinnville has done so far
Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.
Sources
Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.
Last updated September 30, 2026 · First published September 30, 2026
Questions about the City of McMinnville breach
Take control of what happens next.
Monitoring for misuse of your information, removal of what else is out there, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.