What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
McMinnville said information that may have been accessed and copied without authorization between June 1 and July 18, 2026, could include a person’s name, driver’s-license number, and/or Social Security number. Separately, cybersecurity specialist Chuck Dornon told KOIN 6 News he saw a wider range of city records online, but said he could not authenticate every file or determine how many people were affected. If you may be affected, monitor your accounts and credit reports and consider freezing your credit with all three major bureaus.
What information was reportedly exposed?
What McMinnville said, according to KOIN
KOIN’s account of the city’s September 29, 2026 notice said potentially affected information varied by person and could include a name, driver’s-license number, and/or Social Security number. That is the city’s reported description of potentially affected identifiers, not confirmation that every person’s records contained all three.
As an Amazon Associate I earn from qualifying purchases.
What the specialist said he saw
Dornon, identified by KOIN as the CEO of Alexonet, told the station that he saw a broader mix of records, including tax, password, banking, human-resources, and police material. Those observations should not be treated as a confirmed inventory of city files or proof that each category belonged to an affected resident: KOIN reported that Dornon’s notes acknowledged he could not authenticate every file or establish the number of affected people.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Dornon called the material “a treasure trove of information” and said, “This is probably the easiest form of information I’ve come across in a breach.” These are his characterizations, not a formal assessment of the complete dataset. KOIN also reported his estimate that the site had recorded 53,000 visits as of Wednesday; visits do not establish unique visitors, downloads, or misuse.
#1 Best Overall
What happened, and when?
| Date | Reported event |
|---|---|
| June 1–July 18, 2026 | The city said information may have been accessed and copied without authorization during this period, according to KOIN. |
| Around July 15, 2026 | The city reportedly noticed unusual network activity. This is the reported detection of activity, not necessarily the date the city determined that personal information was compromised. |
| August 6, 2026 | Dornon told KOIN he learned of the breach through dark-web monitoring sites. |
| September 22, 2026 | The city’s review to identify sensitive information and the people associated with it was described as “in-part completed,” KOIN reported. |
| September 29, 2026 | The city reportedly issued a notice announcing notification letters and describing potentially affected identifiers. |
| October 1, 2026 | AOL’s republication of KOIN’s report showed an update time of 12:30 a.m. UTC. |
KOIN reported that the city’s investigation remained ongoing. The station said the city did not answer when it determined personal information had been compromised, when individual notices began, or how many people were affected; the city said it had no further comment at that time.
What should you do if you may be affected?
- Read any notice you receive. The city reportedly sent letters to people it identified as potentially affected. Check the notice for the specific information involved and instructions that apply to you.
- Review account statements and credit reports. Look for unfamiliar transactions, new accounts, or other activity you do not recognize. The city reportedly recommended monitoring both statements and reports.
- Consider placing a credit freeze with each bureau. KOIN said the city recommended free freezes with Equifax, Experian, and TransUnion. A freeze at one bureau does not freeze your reports at the other two.
- Ask the city whether you were identified as affected if you did not receive a letter. KOIN reported that the city listed 1-833-544-7562 for assistance. Its reported hours were Monday through Friday, excluding major U.S. holidays, 8 a.m.–8 p.m. Eastern (5 a.m.–5 p.m. Oregon). Because the response is ongoing, confirm that the number and hours are still current before relying on them.
What is known about Oregon’s notification timeline?
KOIN’s report summarized Oregon law as generally requiring notice as quickly as possible, without unreasonable delay, and no later than 45 days after discovery or notification of a qualifying breach. The date unusual activity was noticed does not, by itself, establish when the legal notification period began. KOIN reported that the city did not answer when it determined personal information was compromised, so the dates available in the report are not enough to conclude whether the city met or missed a legal deadline.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What remains unclear?
- The number of people whose information was affected has not been stated in KOIN’s account.
- The city has not publicly clarified, in the reporting available, when it determined personal information was compromised or when individual notifications began.
- Dornon’s broader categories of records are his observations; they are not a verified city inventory, and he said he could not authenticate every file.
- The city’s investigation was still ongoing when KOIN reported the notice.
The account of the city notice and its response details here comes from Joelle Jones’s KOIN 6 News report, republished by AOL and updated October 1, 2026: AOL republication of KOIN’s report.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
