Microsoft Patches 1,259 Flaws, Including Exploited Outlook Bug That May Expose NTLMv2 Hashes
Amplifon Americas, a U.S. hearing care provider, has disclosed a data breach that affects 1,332,826 people nationwide, according to a Texas Attorney General filing as summarized by BreachTally on Nov. 6, 2026.
Amplifon’s security incident notice says the exposed data includes names, dates of birth, government ID numbers, and health and insurance information, and that Social Security numbers or financial information were affected for a limited number of individuals. Amplifon has not publicly confirmed the total, and the company says it is not aware of any fraudulent use of the information.
An unauthorized third party obtained files from Amplifon’s systems between Jan. 18 and Feb. 8, 2026, according to the company’s notice. Amplifon says it detected suspicious activity on Feb. 11, 2026, notified law enforcement, and disabled impacted accounts.
The notice says a review of the affected data indicated on Oct. 6, 2026 that certain personal information may have been impacted. That is nearly eight months after detection, and the notice does not explain the timeline. Amplifon says it will notify people for whom it has a valid mailing address, and its Texas filing lists U.S. Mail and a website posting as the methods of notice.
Amplifon has not said how the attackers got in. As of Nov. 9, The Record reported that no hacking group had claimed responsibility. Amplifon also filed notices with state officials, including in Texas and Vermont. The Texas Attorney General’s breach report listing, published Nov. 6, 2026, shows 85,804 Texans affected.
What was exposed varies by person, and your notice letter lists which of your information was involved. Amplifon’s notice names these categories:
According to Amplifon, Social Security numbers or financial information “may also have been impacted” for “a limited number of individuals.” The Vermont Attorney General’s breach notice listing for Amplifon names Social Security numbers and health records, and the Texas listing includes Social Security number information among the types affected.
Criminals can use a Social Security number to try to open new credit accounts in your name, which a credit freeze blocks, or to file a tax return in your name, which the IRS Identity Protection PIN is designed to prevent. Health insurance and medical record details add a separate risk: medical identity theft, which happens when someone uses another person’s information to obtain medical care.
Amplifon says it is not aware of fraudulent use so far. The steps below apply whether or not any misuse has shown up.
Read the notice closely, confirm it is genuine, and note which of your information it says was involved. Amplifon’s Texas filing shows that notice was provided by U.S. Mail and a website posting, and the company’s notice says it will notify people for whom it has a valid mailing address.
If you used Amplifon hearing care services and did not get a letter, call the hotline on the notice page to ask whether your information was involved. The notice says Amplifon will notify people with a valid mailing address, so a missing letter does not by itself show that your information was not involved. The steps below apply either way.
Signs of misuse tend to appear in your credit reports, your medical and insurance statements, and the messages you receive.
| Warning Sign | Why It Matters |
| An Explanation of Benefits for care you did not receive | The FTC lists this as a warning sign of medical identity theft. |
| A medical debt collection notice you do not recognize | The FTC advises checking credit reports for unfamiliar medical collections after a medical identity theft. |
| Accounts or credit inquiries you did not open | Someone may be using your identity details to seek new credit. |
| A call, text, or email about the breach that asks for your SSN, payment, or login details | Messages about a breach can be copied by scammers. Use the phone number on your letter or on Amplifon’s official notice page instead. |
Start by confirming what was exposed, then block new credit in your name and watch your accounts and statements.
Yes, if your notice says your SSN or financial information was involved. The FTC says there is no cost to place or lift a freeze, and that while one is in place nobody can open a new credit account in your name, including you. A freeze does not close existing accounts.
Place the freeze separately at Equifax, Experian, and TransUnion. A free fraud alert, which lasts one year, is a lighter option, but unlike a freeze it does not block lenders from viewing your report.
If your notice says your SSN was involved, or you see signs of misuse, freeze your credit first, then work through these steps.
McAfee’s identity theft recovery guide covers additional steps.
Amplifon disclosed the breach in early November 2026, and more details may emerge as the company and regulators release information. Whatever your letter says, the most important protective step is a credit freeze at Equifax, Experian, and TransUnion, because it blocks new accounts opened with exposed identity details.
Yes. Amplifon says an unauthorized third party obtained files from its systems between Jan. 18 and Feb. 8, 2026, and that it detected suspicious activity on Feb. 11. BreachTally’s summary of the Texas filing lists 1,332,826 affected people nationwide, a total Amplifon has not publicly confirmed. The Texas Attorney General’s listing shows 85,804 Texans affected.
Amplifon’s notice lists names, contact information, dates of birth, driver’s license and other government ID numbers, health and medical information, and health insurance information. Social Security numbers or financial information were affected for a limited number of individuals, according to the company.
Amplifon has not publicly explained the timeline. Its notice says a review of the affected data indicated on Oct. 6, 2026 that certain information may have been impacted, nearly eight months after the Feb. 11 detection.
Amplifon says it is offering 24 months of free credit monitoring and identity protection services to certain individuals, including those whose SSN or financial information was affected. Monitoring and a freeze do different jobs: monitoring alerts you to activity, while a freeze blocks new accounts from being opened in your name.
The post Amplifon Data Breach Reportedly Affects 1.3 Million: How to Protect Your Personal Data appeared first on McAfee Blog.
Microsoft did another four-digit patch drop today, releasing updates to fix almost 1,100 security vulnerabilities in its Windows operating systems and supported software. This month’s Patch Tuesday addresses 63 critical flaws — including a zero-day in Microsoft Outlook — and comes amid important security updates from other software makers, including Adobe, Apple, Google and Mozilla.
Image: Shutterstock.com. Diorama by @zepp1969.
November’s patch release from Redmond tackles 1,093 vulnerabilities, fixing 63 “critical” flaws that can be exploited to seize control over a Windows system with little or no help from users. Nearly half of those critical bugs are remote code execution vulnerabilities. Overall, 535 of the flaws addressed this month allow an attacker to elevate their privileges on a vulnerable device.
This latest round of updates means Microsoft has shipped more than 5,100 security patches so far this year, a staggering number considering that a year ago Microsoft was averaging around 100 patches per month. Microsoft credits advances in artificial intelligence for helping to find (and fix) such a large volume of security bugs in recent months. Last month, Microsoft pushed more than 1,400 fixes.
According to Redmond, just one of the flaws is already seeing active exploitation: CVE-2026-124194, a spoofing bug in Outlook. The advisory for CVE-2026-124194 says it affects Microsoft 365 Apps for Enterprise and editions of Microsoft Office.
Several other major software makers pushed security updates this week to fix critical weaknesses in their products. Apple on Monday released out-of-cycle security updates to fix at least nine vulnerabilities in iOS/iPadOS, macOS, watchOS and visionOS. Among the weaknesses reportedly fixed in Apple’s release include an iMessage flaw that could let a remote attacker join a group chat and receive its messages; the updates also fix a separate iMessage flaw that could let someone added to a group access messages sent before they joined.
Lee Neely, an instructor at the SANS Institute, noted that Apple backported the fix to iOS 18.
“I take notice when Apple releases fixes to more than two versions,” Neely wrote in a SANS newsletter today. “You really need to get to version 27.2.1 of their OSes and push folks who are holding onto devices which cannot run the current version. The best plan often involves setting an upgrade date for old hardware. Run through all your Apple devices and make sure everything is up to date, don’t assume the fixes went out automatically.”
Google this week released Chrome version 157.0.8103.50, which resolves nine security holes, including CVE-2026-125350, the sixth zero-day vulnerability this year for Chrome (this bug also is being patched in Chromium-based browsers like Edge). The latest Chrome version follows its November 3 release, which fixed 213 vulnerabilities. A new version of Mozilla Firefox out today (Firefox 160) resolves almost 100 CVEs, about half of them high severity.
Adobe today released patches for at least 110 vulnerabilities across a range of products, with nearly half of the flaws rated high severity. Adobe said there is no evidence any of the security holes it addressed this month are being actively exploited.
Chris Goettl, vice president of product management at Ivanti, said it’s easy for security teams at large enterprises to feel overwhelmed by the volume and criticality of patches from Microsoft lately. But he notes that while some 95,000 vulnerabilities have been assigned CVEs this year across all vendors, only 217 have so far this year been added to the Known Exploited Vulnerabilities (KEV) list maintained by the U.S. Cybersecurity and Infrastructure Security Agency (CISA).
“Roughly four in ten of this year’s exploited vulnerabilities sit in operating systems, endpoint software, browsers, and server platforms, which a continuous patch strategy can close quickly,” Goettl said.”The rest calls for exposure management alongside patching, especially the 44% that sit in edge devices and IT management or remote access tools, the internet-facing systems that hold privileged access. Teams that can quickly identify those assets, confirm exposure and act on confirmed exploitation can focus on the small slice of vulnerabilities attackers are actively using, while the rest stays on the normal patch cadence.”
Please don’t neglect to back up any important data if you haven’t recently; generally speaking, this is a task best accomplished before applying operating system updates. As ever, if you experience any issues installing this month’s bundle of love from Microsoft, please drop a comment about it in the space below.




This is simultaneously the most boring yet exciting blog title I've written in a long time. How you pay for services isn't exactly a sexy topic, but it solves a problem that's been a massive bugbear for a long time.
Here's a brief history of the issue: many organisations have policies that make it extremely hard to purchase goods and services with a credit card. I wrote about this more than two years ago now, where I referred to "Neville" in the procurement department who, because "reasons", demanded an invoice in advance and payment via electronic funds transfer (EFT) only. That ultimately means the world's most popular way to make online payments is out of reach for them. Unfortunately, until today, that was the only way we could take payment via Stripe, which processes all our online HIBP purchases. That left only two options for orgs in this situation:
The problem with the first option is obvious. The second option "solved" the first problem by allowing a company to pay a reseller by EFT, who then paid us by card. The reseller would then mark the price up (often significantly), slow the whole process down, log countless tickets with us (despite the existence of a dedicated portal for them), and frankly, just be a pain in the arse for everyone. It's hard to express the level of disdain I have for most resellers, and I even still have a 1,381-word draft blog post titled "That's it - Resellers are now Banned from Have I Been Pwned", which I held back from posting. Why? Because I've walked in the shoes of the folks trying to purchase our services who are just trying to get their job done, and Neville has told them they can't pay by card. That was me in a previous life, and it sucked. We kept resellers solely to support those people.
But today, HIBP's subscription page has something all new on it:

Stripe has given us early access to EFT payments in Australia. They've been available in the US for a while, but as an Aussie company and with global financial systems being what they are (i.e. not always the most flexible), we just didn't have that option. Until now. So, we've added EFT as a payment method to our Pro and High RPM plans and kept the entry-level Core ones on card only, as there's some additional overhead on our end. You'll see these every time you go to purchase an eligible subscription:

When you choose to pay by bank transfer, you're given a form for your company details (this is how we calculate any applicable taxes), then a Stripe payment link which loads something similar to the following:

The first thing is that, being an Aussie company with an Aussie bank account, we need to reflect EFT payments in AUD rather than USD. It makes sense when you think about it: we do USD for all the existing products paid for by card, and whatever the FX conversion gods decide is the corresponding Aussie amount eventually lands on our end. But that's a model where the card is charged, and access is granted immediately. For EFT, funds flow through the wires, do FX conversion for non-Aussie purchasers, land in the target account and then Stripe webhook magic enables the service. We need that exact amount to land on our end, so we can't be rolling the dice on what exchange rate we're going to get; hence, Stripe requires us to charge in the target currency. The products are exactly the same price based on the rate we currently see via Stripe purchases today (about 69 American cents per Aussie dollar), we'll just have to see if that's revised in the future with any major currency fluctuations.
Next are the banking details. Pretty straightforward, and I'm sure we've all made payments to an account like this before. The main thing is that the account number is a virtual one, which is how Stripe reconciles money that comes in from a previously raised invoice. When you sell a very limited number of products and a bunch of customers are buying the same one, this is how Stripe is then able to reconcile who has paid for what. If you really want to geek out on bank payments, Stripe has a dedicated EFT explainer page.
And finally, subscriptions in HIBP begin as soon as the invoice is raised, but access to the service only begins when payment is made. You can see the problem if we didn't do it this way: bad guy spins up the service and immediately starts using it then just never pays. But this all ties into the quote ecosystem in the existing HIBP dashboard, so it's easy to generate a quote, go flick it to Neville, get it approved, then raise and pay the invoice straight away.
As I said in the opening, it's not the most exciting topic, but it's a major thing for us and the customers who were left with only bad options if they genuinely couldn't pay by card. In the aforementioned draft blog post on binning resellers, I'd written about how we'd seen markups of up to 131% (so yes, more than double the price!), with absolutely zero value add (i.e. they don't do any product support, that remains entirely on us). But the burden resellers really put on us is the support they require to make purchases; in that same draft post, I calculated that resellers accounted for 0.86% of all sales but 43% of all support tickets. That's just nuts, especially for such a small team (although Bruce has helped enormously).
We hope this makes life easier for a bunch of people who were previously stuck between a rock and a hard place, and that includes all the "Nevilles" out there too. This is all now live and accessible via the pricing page. If you run into any issues, Bruce is standing by in the support portal.
A while back, I had released a blog showing that NTLMv1 downgrade attacks still work on Windows Server 2022! While it isn't a default setting, it's still a misconfiguration to potentially look for.
If a DC’s LmCompatibilityLevel is set to 0-2, you can coerce authentication, strip Extended Session Security (ESS), and obtain an NTLMv1-SSP hash that’s crackable with a rainbow table. :)