CISO Tribune

Town Square · Monday, November 16, 2026

Exchange Online outage reused as a phishing lure and 5 more

By Hadass Liza Bitton · November 16, 2026 · 6 stories

Sysadmins spent the day picking apart the root-cause report on Microsoft's Exchange Online incident, while Hacker News users traded reports of tailored scam email after posting their addresses and a researcher argued that vm2's own repository tracks unfixed sandbox escape paths. What holds up: Microsoft has warned that phishing lures pose as outage notices threatening to delete held mail, the Tor Project has shipped 0.4.9.17 with denial-of-service (DoS) fixes as the attack on relays continues, and Coles confirms it is investigating a cyber incident and says there is no evidence customer data was taken; the root-cause details, the scraping theory and the claimed inventory of a criminal market that uses artificial intelligence (AI) to label and search infostealer victims remain unproven. Our view: treat any outage email that threatens to delete mail as a lure, and review any reliance on vm2, since public advisories already show the escapes keep coming.

Today's board

  1. 1Coles investigates cyber incident, says no evidence customer data was takenConfirmed
  2. 2Tor Project ships 0.4.9.17 with DoS fixes as attack on relays continuesConfirmed
  3. 3Microsoft outage report circulates as phishing lures reuse the Exchange Online incidentPartly confirmed
  4. 4Researchers describe a criminal market that uses AI to label and search infostealer victimsNot confirmed yet
  5. 5Hacker News users report tailored scam email after posting addresses; method unprovenNot confirmed yet
  6. 6Researcher says vm2's own repository tracks unfixed sandbox escape pathsPartly confirmed

Story 1

Coles investigates cyber incident, says no evidence customer data was taken

The Australian supermarket group confirmed an incident and is working with the national cyber agency. The type of attack, entry point and attacker are unknown.

Our verdictConfirmed

Coles states on its own corporate updates page that it is investigating a cyber security incident, and Nine reported its ASX statement.

What people are saying

Coles has posted a notice on its corporate updates page saying it is investigating a cyber security incident. On X, some posts were blunter, with one describing a cyber attack early Monday. Several others complained it offered almost no detail.

What holds up

The incident is confirmed by Coles itself. According to Nine, Coles said in an ASX statement on Monday that it had not identified any evidence that customer, team or supplier data had been compromised. Nine reported that the app, website, Flybuys and gift cards still worked, while a small number of customers had problems with Liquorland click-and-collect. Coles said it was working with the Australian Cyber Security Centre (ACSC) and global experts to contain its IT systems.

The nature of the attack is not established. As Shattered noted, Coles has not said what kind of attack it faced, how the intruders got in, which systems they touched or when it spotted the problem. Our verdict: the disclosure is confirmed, and scope and attribution remain open.

Inside the threads

The Hacker News thread split between Australians who called the incident potentially massive, given Coles is half of a national supermarket duopoly, and readers abroad who saw just another breach. One commenter, citing Reddit posts, said internal staff systems and inventory processes appeared to be affected. That is secondhand and unverified. Another debated why Coles had involved the ACSC, and a reply said the company is part of critical infrastructure. A password-change prompt drew a question about plain-text storage, and others answered that rotating secrets is standard advice whether or not data was taken. One X post tied the incident to freezer problems at grocery stores, which we treat as speculation.

Our take

We read "no evidence" as a statement about findings so far, not a finding that nothing was taken. Early retail statements tend to lead with what still works, and that is what this one does. The thread's focus on whether customer data leaked is understandable, but in our reading the operational signals deserve more attention: a click-and-collect problem and reported effects on staff systems would point to an availability incident, not only a privacy one. Australian rules require an organization that suspects an eligible breach to assess it within 30 calendar days, so we expect fuller answers within weeks. Until then, the bigger near-term risk for most organizations is phishing that rides the headlines.

What to do

  • If you supply or integrate with Coles, ask your contact for direct updates and rotate any shared credentials or API keys as a precaution.
  • In our reading, if you operate in Australia, confirm your playbook covers the 30-day breach assessment and the 72-hour report required after a ransomware payment.
What the verdict rests on (4 sources)

Story 2

Tor Project ships 0.4.9.17 with DoS fixes as attack on relays continues

The release targets relay denial-of-service defenses during an ongoing DDoS. Operators report the disruption has not ended.

Our verdictConfirmed

The Tor Project's own release announcement on its forum states the release responds to an ongoing DDoS attack and asks relay operators to upgrade, and SecurityWeek reports the same.

What people are saying

The claim is that the Tor Project pushed out a rapid security release to help relays survive an ongoing distributed denial-of-service (DDoS) attack, and that relay operators should upgrade now. The project's release announcement says the release responds to an attack that has hit most relay operators. On a Hacker News thread, one person running a relay at home said the attack left their download speed down 99% from normal.

What holds up

The core claim holds. The Tor Project announced version 0.4.9.17 on November 13 with several security fixes. It singled out one fix as especially important for relay DoS defenses related to IPv6 handling.

The project said relays across the network are being overwhelmed by a massive flood of client circuits. It said it is evaluating additional defenses and expects further releases soon. It asked relay operators to upgrade as soon as possible and said no action is needed after upgrading.

SecurityWeek reported that the release comes less than three weeks after 0.4.9.15, which added three DoS protections against what the project called a thunderstorm of directory requests. It also reported that relay operators say the latest update has not ended the disruption.

One operator wrote on the Tor forum that the attack took on a new form about ten minutes after their relay was upgraded. That operator said the relay's unresponsiveness caused it to lose its hidden service directory (HSDir) role. The same operator warned that the attacker could be able to deanonymize and track onion services, a warning the Tor Project has not issued.

Inside the threads

The home relay operator said the problem went away once they stopped their relay from serving as a guard node. Several commenters moved quickly to motive, with one blaming a state actor without offering evidence. Another asked whether the flood is meant to push traffic toward adversarial relays, and a reply called that "Reasonable to assume, as a threat-modeling step." A practitioner noted Tor has added proof-of-work challenges, but suggested this attack may hit before those defenses trigger. Much of the rest of the thread drifted into complaints that Tor is still slow and unreliable. We read the state-actor and traffic-steering ideas as speculation for now.

Our take

We think this is mainly an availability story, and the Tor Project's own words support taking it seriously. In our reading, the deanonymization worry is the part to watch rather than repeat: it comes from one operator, and the project has not echoed it. We think the traffic-steering theory is a fair way to frame risk, because knocking honest relays offline could in principle shift where circuits go, but it remains unproven. For most enterprises Tor is not in the path of daily work, so we would not escalate this to a board topic. Our take is that the underrated exposure is the team that runs an onion service for tip or whistleblower intake, or collects threat intelligence over Tor, and has never tested what happens when the network degrades for weeks. We also think a home or office relay can quietly consume bandwidth under an attack like this, which is a reason to know where your staff run one.

What to do

  • Find out whether anyone runs Tor relays on corporate networks or cloud accounts, upgrade them to 0.4.9.17 now, and plan for follow-up releases.
  • If you run an onion service for whistleblower or tip intake, test its reachability and publish a fallback channel.
  • If threat intelligence collection depends on Tor, expect slower or failed collection and adjust coverage expectations with your team.
  • Treat the deanonymization warning as unverified, but review what your onion service would expose if its location became known.
What the verdict rests on (2 sources)

Story 3

Microsoft outage report circulates as phishing lures reuse the Exchange Online incident

Microsoft warned of fake outage notices threatening to delete held mail. Sysadmins are picking apart the root-cause report.

Our verdictPartly confirmed

Microsoft Threat Intelligence's own post, reproduced by IBTimes Singapore and reported by the Times of India, establishes the phishing warning, while root-cause details rest on quotes in a Reddit thread.

What people are saying

Commenters in an r/sysadmin thread are dissecting what they describe as Microsoft's post-incident report (PIR) on the November 12 outage. Separately, an International Business Times article says attackers are falsely claiming that email delayed during the outage will be deleted unless users click a link. In an r/cybersecurity thread, a commenter who answers reported phishing said their team had received a batch of the messages.

What holds up

Wikipedia's entry on the outage says it ran from November 12 to 14 and hit Outlook, Teams and Copilot. After 16 hours, the outage was mostly narrowed down to Exchange, which powers Microsoft's email services.

The phishing warning comes from Microsoft itself: the Times of India reports that the company said in an X post that criminals are sending phishing emails that impersonate service health notifications. Microsoft says the messages reference the legitimate Exchange Online incident EX1550543. Observed subject lines follow the pattern "Outage - [six-character code]." Similar messages targeted organizations across multiple US sectors. Microsoft calls the activity consistent with credential phishing but says credential collection and malware delivery have not been confirmed.

On the root cause, Wikipedia says a Microsoft executive summarized it in a post on X, describing three issues in the company's networking gateway servers. Thread commenters quote the report as saying a contention issue is worse on machines with more cores and newer hardware than the ones load testing focused on.

In our reading, the outage and the phishing warning are established, while the finer root-cause details now spreading are partly confirmed at best.

Inside the threads

In r/sysadmin, one commenter said that either Microsoft needs a better team to write its status updates or the report is not fully honest. Practitioners pushed back that few organizations will pay for a test environment that fully matches production. Several commenters zeroed in on a quoted line saying a separate issue let the failure cross the normal bulkheads between partitions. One commenter blamed staff cuts made earlier in the year. Another corrected a figure being repeated, saying the 60,000 were offered a voluntary buyout and are not leaving until December 31. In r/cybersecurity, the phishing triage commenter said their team was blocking the campaign.

Our take

We think the phishing campaign deserves more of a security leader's attention this week than the root cause. In our reading, any outage your users have heard about is now a ready-made pretext, and attackers will reuse the next one the same way. We think the testing gap commenters fixated on is overblown as a lesson for most teams, since few of them can mirror production at that scale either. Our take is that the underrated point is the bulkhead failure, because that is the question to put to any provider that hosts your email. We think continuity plans that assume one region fails alone deserve a second look.

What to do

  • Brief staff that any message threatening to delete held email should be reported, not clicked.
  • In our reading, have your email team search recent mail for the subject pattern and sender details Microsoft published, then check who clicked.
  • If you run Microsoft Defender for Office 365, confirm your Safe Links policies are in place and cover all users.
  • Ask your Microsoft account team how the partition bulkheads failed and what changed, and fold the answer into your email continuity plan.
What the verdict rests on (3 sources)

Story 4

Researchers describe a criminal market that uses AI to label and search infostealer victims

Hudson Rock says a forum-advertised service writes a profile for each infected computer. The operator's inventory claims are unverified.

Our verdictNot confirmed yet

The marketplace's features rest on one research team's review of the operator's own advertisement and screenshots on InfoStealers, and the inventory figures are the operator's assertions.

What people are saying

Researchers writing on InfoStealers say a new service advertised on cybercrime forums is adding a layer of interpretation to the sale of infostealer logs. Buyers can search descriptions of each infected computer using natural language and filter by country, operating system and price. The site's front page credits the work to Hudson Rock, which analyzed several of the logs on offer.

What holds up

A forum advertisement dated November 14, 2026, promotes the marketplace. The operator claims tens of millions of logs, more than one billion parsed accounts and AI analysis of every log, with prices starting at $0.25.

The researchers say those inventory figures, coverage claims and prices are the operator's assertions. They say the screenshots do show an interface with detailed computer descriptions, an AI-labeled search tab and individual listings for sale.

In our reading, their clearest example is a search for remote access into a healthcare provider. It returned a $10 listing titled "The Ophthalmology Clinic Front Desk Dump." The listing describes a Canadian clinic workstation and refers to Citrix virtual private network (VPN) credentials.

The broader trend has independent backing. Flashpoint's midyear report recorded 7.4 million infected hosts and devices in the first half of 2026. It says threat networks are connecting AI agents directly to raw log supply chains.

We rate the specific marketplace claim unconfirmed. Its features rest on one team's reading of the operator's own advertising, and its scale rests on the operator's word.

Inside the threads

On Reddit's r/cybersecurity, one reaction was weary resignation: shut the internet down. Another commenter wrote "It doesn't work," saying a search returned only their own IP address. In our reading, that comment does not describe a test of the criminal marketplace. It is not evidence against the research. A separate Bluesky post about infostealer malware that steals ChatGPT, Claude and Codex tokens is a different story. We think readers should keep the two apart.

Our take

The AI angle is the headline, but the real shift is triage. Stolen logs have long been cheap and plentiful. The hard part for a buyer was finding the one machine that opens a door worth opening. A searchable description of who uses the computer and where they work removes that friction.

The operator's billion-account figure is marketing, and we would not plan around it. In our reading, the underrated detail is the type of machine on offer: a clinic front desk, a contractor's family computer. Those are unmanaged or lightly managed endpoints that still hold work credentials.

If your remote access depends on a password and a session that outlives a reset, this service makes you easier to find.

What to do

  • Monitor for your corporate domains in infostealer log feeds, and fold the results into your threat intelligence program.
  • When an employee's credentials surface in a log, revoke active sessions and tokens as well as resetting the password.
  • Require phishing-resistant multifactor authentication (MFA) and device posture checks for VPN and remote desktop access, especially from personal or shared computers.
  • Review front-desk and shared workstations in clinical and branch settings, where one infection can expose remote access for a whole site.
What the verdict rests on (3 sources)

Story 5

Hacker News users report tailored scam email after posting addresses; method unproven

A Tell HN post says the site is being scraped for scam targets. Users report spam at posted addresses, but no one has shown who is behind it.

Our verdictNot confirmed yet

The claim rests on user reports in the Hacker News thread itself, with no primary or independent confirmation of the method, the sender or the scale.

What people are saying

A Tell HN post on Hacker News titled "HN is being scraped for emails to scam" drew 107 points and 36 comments.

What holds up

The thread shows users reporting spam and scam mail at addresses they had posted on the site. One commenter said a unique address they put in a hiring post had been receiving automated, template-based mail, and another said posting in the hiring thread had half burned their primary developer address.

In our reading the verdict is unconfirmed. These are user reports, and the method, the sender and the scale remain unproven.

The broader practice is real. In an earlier thread about companies scraping GitHub activity, a GitHub representative said such scraping violates GitHub's terms of service and noted that every Git commit contains a name and email address. The BBC reported in 2021 on a scraped database of 700 million LinkedIn users, which LinkedIn said included information scraped from LinkedIn as well as information obtained from other sources.

Inside the threads

Some commenters were unsurprised; one wrote "I'd be more surprised if it weren't." Others traded hygiene advice: one said switching to a throwaway address shown as an image in the hiring thread had greatly improved the signal-to-noise ratio. On targeting, a commenter asked whether the poster had ever mentioned AWS on the site, and the poster said they had mentioned working with AWS. The data broker link is speculation: one commenter said they were guessing an old throwaway address appeared in a broker database.

Our take

We think the headline overstates what is known. Nothing here shows a single campaign built on Hacker News, and junk mail at public addresses is not new. What we think is underrated is the personalization question. A cloud billing lure sent to someone who has talked publicly about their cloud work is exactly the kind of message that gets past a busy engineer. Your developers leave this trail every day through commits, project launches and job hunting, often with work addresses. In our view the realistic risk is credible phishing and fake job offers aimed at technical staff, not a breach of the forum.

What to do

  • Encourage engineers to use alias or role addresses, not work or primary personal addresses, for commits, hiring posts and public project contact pages.
  • Add tailored lures to phishing exercises, such as billing notices from cloud providers your teams use. The FBI advises people to look up a company's phone number themselves and call to check whether a request is legitimate.
  • Tell staff to report unsolicited job offers that ask them to install software or run a test project, and route those reports to your security team.
  • Confirm multi-factor authentication is enforced on cloud and code hosting accounts. The FBI says to set it up on any account that allows it and never disable it.
What the verdict rests on (4 sources)

Story 6

Researcher says vm2's own repository tracks unfixed sandbox escape paths

A blog post reads vm2's commits as a list of open escape routes. Public advisories confirm the escapes keep coming. The rest is one researcher's reading.

Our verdictPartly confirmed

GitHub's advisory and the NVD record confirm repeated vm2 sandbox escapes, but the claim that the repository lists live, unfixed escape avenues rests on the researcher's own quotations.

What people are saying

A researcher's blog post argues that vm2, a sandbox for running untrusted code inside Node.js, documents its own unfinished security work. The post says the project's next advisories already sit in the repository under "considered and deferred," under "monitoring," and under a README heading. The researcher's conclusion is blunt: "vm2 is not a wall. It is a list."

What holds up

The post quotes a commit message for a security fix stating that a nesting configuration "remains an escape hatch" and that a broader fix "was considered and deferred." According to the researcher, that note sits under a heading the maintainer wrote as "What this fix does NOT close." The researcher says the fix shipped on May 1, 2026, with a Common Vulnerabilities and Exposures (CVE) record stating the issue is patched. The post also counts eighteen advisories closed in four releases between February 17 and May 3, thirteen of them in a single release.

Primary records confirm that the escapes keep coming. A GitHub advisory states that a vm2 sanitization step could be bypassed, allowing attackers to escape the sandbox and run arbitrary code. The National Vulnerability Database entry lists versions prior to 3.10.2 as affected. A FortiGuard outbreak alert tracked four earlier escape CVEs and warned that attackers could gain remote code execution on the host.

Our verdict: partly confirmed. The record of repeated sandbox escapes is established. The reading that the repository lists live, unfixed escape routes rests on the researcher's interpretation of the project's commits.

Inside the threads

In our reading, the vm2 post landed in a wider argument about whether code containment works at all. One post on X put it plainly: "Sandbox escapes remain unsolved." That post came in a discussion of artificial intelligence (AI) model behavior. Another post sorted guardrails for AI agents that read outside text and can take action, using one test: whether each holds when the attacker adapts. We think the overlap matters, because teams wiring agents to execute code face the same problem vm2 does. The speculative part is the blog's framing: the "next three advisories" are a forecast built from deferred items, not disclosed vulnerabilities.

Our take

We think the researcher's evidence matters more than the rhetoric. A maintainer who writes that a fix does not close a class of escape is being honest, and is also confirming that the product's core promise has known gaps. The researcher describes one escape route that drew five fixes over thirty-two months, from three different people, at the same call site. In our reading, that pattern fits the public advisory record. The claim of pre-written advisories is overblown. The exposure through dependencies is underrated: FortiGuard's alert noted that Backstage, a developer portal platform, used vm2. Our take is that any in-process JavaScript sandbox is a convenience, not a security boundary.

What to do

  • Inventory vm2 across your own code and third-party software, including transitive dependencies, and ask suppliers whether their products embed it.
  • Where vm2 remains, upgrade to the current release and do not combine nesting with module loading.
  • Move untrusted code, including AI agent tool execution, into process, container or virtual machine isolation with no access to host credentials.
What the verdict rests on (4 sources)

How Town Square works

Every day we read what the security community is discussing on Hacker News, Reddit, Mastodon and Lobsters, and what search shows of the conversation on X. For each story we check the claim against primary sources, give a verdict, digest what the threads said, and say what we think.

What each verdict means

The CISO Tribune briefing

Every verified CISO move and one piece of analysis, weekly.

Unsubscribe any time. See the privacy policy.