Capstone Technologies Group

Monthly Briefing · November 2026

Four stories this month, and none of them needed an unpatched flaw. Each one ran on something working exactly as designed: Microsoft's real sign-in page, a Teams chat feature that is on by default, remote-support tools that IT departments use every day, and an online shop that sold ready-made phishing kits to anyone who paid. In most of them, the step that let the attacker in was taken by an employee who believed they were doing the right thing. That is why this month's fixes are settings and written rules, not reminders to be careful. If you do one thing before the next issue, ask whoever manages your Microsoft 365 one question: can people at other companies start a Teams chat with our staff?

Fake IT Support in Teams: From Spam Flood to Remote Control in Under 15 Minutes

Arctic Wolf tracked more than 400 incidents of fake IT support in Teams, and many started the same way. An employee's inbox suddenly fills with hundreds of newsletter sign-ups. Minutes later a Teams chat or call arrives from "IT support," offering to fix the flood the attacker just caused. The employee is talked into opening Quick Assist, the remote-help tool built into Windows, and the time from the first reply to attacker code running was under 15 minutes. The chat itself never passes through your email filter. Teams external access is on by default, so anyone at another Microsoft 365 company can chat with and call your staff, and in 30 to 40 percent of cases the fake help desk used Microsoft's default onmicrosoft.com addresses, which take minutes to set up. Arctic Wolf did not name the group behind these incidents, though ransomware crews including Black Basta have used this route before. The single most important change is to limit outside Teams contact to the companies you actually work with. Pair it with a written rule for staff: your IT support will never reach them through an external Teams chat. The write-up lists more steps, including limiting Quick Assist to your IT staff.

See every step, starting with the Teams setting

Phishing Defense Fails When Email Controls Target the Wrong Layer

As reported by CSO Online, a researcher timed how long it takes to build a working phishing site: under 24 minutes, on a domain that cost about a dollar. That domain is what your email filter blocks, and the attacker replaces it before lunch. The kits doing damage now do not show a fake login page. They pass your employee through to Microsoft's real sign-in page, let them answer a real multi-factor prompt, and keep the session Microsoft hands out at the end. Multi-factor confirms who started the session. It has nothing to say about who holds it afterward. In the case examined, the lure came from a real company's hacked mailbox, so every sender check passed. For a practice or firm, that one session typically opens the mailbox, the shared files and the payment threads an invoice fraud needs. The write-up lists the fixes, starting with security keys or passkeys for anyone who can move money, and the response step that is easy to get backwards: end the stolen session first, then reset the password.

See the fixes, starting with the accounts that move money

Prefer the short version? Read the blog post

Microsoft Takes Down YAM Store, the Phishing Shop Behind 1 Billion Messages

Microsoft's Digital Crimes Unit shut down YAM Store, an online shop that sold ready-made phishing kits and fraudulent Microsoft and Google accounts. Its customers sent more than 1 billion messages to over 75,000 organizations, and more than 750 million of those went to Microsoft customers. Buyers needed little skill. The kits carried more than 2,300 ready-made fake pages impersonating organizations in over 150 countries, healthcare providers, tax agencies and banks among them. They also hid those pages from security scanners, so a link your IT person checks may look harmless while your employee sees a sign-in form. The operators bought domains that real organizations had let expire and rebuilt them to look active, so if your office ever let an old domain lapse, that name may have resale value to someone. Treat the takedown as a pause. The technique and the buyers are still out there. The step to take is passkeys on the accounts that matter. A passkey only works on the real sign-in page, so a fake page cannot capture one to reuse. Microsoft says steps like this slow an intruder and buy time to respond.

See how expired web addresses get reused for phishing

Nine Malware Trends, One Shift: Breaking In Is Now Something Attackers Buy

Infostealers, the malware that quietly copies saved passwords, browser sessions and VPN logins off a PC, now account for 75% of stolen credentials, according to research from Immersive. The haul is sold, and the person who infects the laptop is often not the one who uses the access. Delivery has changed too. A trick called ClickFix shows a familiar "verify you are human" box, says the check failed, and tells the user to press Windows+R, paste and hit Enter. The page has already copied a command, so the employee installs the malware themselves, with no attachment or download for a filter to catch. Where staff have no need for the Windows Run box, it can be switched off. That removes the Windows+R version of the trick, not every version of it. At the far end of the chain, ransomware groups such as Akira and RansomHub copy your data out before they lock anything, so paying for a key does nothing about the copy they threaten to publish. The rule worth adopting now: treat any infostealer alert on any PC as a stolen login for every account used on that machine, sessions included.

See the hardening steps, starting with the Run box setting

Questions about your own office? Email me at .

Brian

See where your office stands

A 15-minute call, then written findings on five areas: dark web exposure, phishing risk, security controls, remote access and employee training readiness. No cost, no obligation, and the findings are yours to keep. We can also send them to your current IT provider.

Book 15 minutes for written security findings

This web copy of the November 2, 2026 issue was updated on November 6, 2026 to state two figures as the source published them, replace one claim that had no named source, and match a few sentences more closely to their sources.