Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Com Vishing Campaigns Shift Toward Healthcare and Australia

Com vishing campaigns show distinct Vortex and Cinder identity paths. Unit 42 reports healthcare targeting and Australian target subdomains in October.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
21 November 2026
Reading time
5 min read
Two separate identity access paths leading toward protected cloud data

Com vishing campaigns tracked by Unit 42 shifted toward healthcare organizations in September 2026, while Australian targets represented a larger share of observed subdomains in October. Unit 42 published the findings on 20 November 2026 and separated two newly identified activity clusters, Vortex and Cinder. Security teams should pair phishing monitoring for organization-specific sign-in lures with identity and cloud access reviews after suspicious help desk calls. A successful initial MFA challenge does not clear later activity.

The comparison below follows Unit 42’s cluster-level observations. It does not treat the clusters as aliases for Bling Libra, another named actor in the wider Com-affiliated activity. The distinct behaviors guide where defenders look first; they do not prove a single operator or a common victim set.

Com Vishing Campaigns: How Do Vortex and Cinder Differ?

Question CL-CRI-1264, Vortex CL-CRI-1274, Cinder
First identified by Unit 42 September 2026 September 2026
Initial access described Callers pose as internal IT support and lead staff to organization-specific sign-in pages using an adversary-in-the-middle proxy. Callers use vishing and later reuse a persistent authenticated session associated with a “keep me signed in” choice.
Persistence or session clue Unit 42 observed unauthorized MFA device enrollment within minutes of authentication. Unit 42 observed session reuse that avoided another Duo MFA prompt.
Cloud data targeted Microsoft 365 mailboxes, OneDrive and SharePoint. SharePoint and OneDrive through scripted access.
Extortion channel observed Microsoft Teams messages sent to employees after data theft. Internal email and Microsoft Teams messages sent from a compromised account.

Read the rows as investigation leads, not a fingerprint for attribution. Unit 42 identifies Vortex and Cinder as separate clusters within broader Com-affiliated activity. Its account does not establish that every suspicious MFA enrollment belongs to Vortex or every persistent session belongs to Cinder.

Why Does the Healthcare and Australia Shift Matter?

Unit 42 says its monitored Com-related domains pointed toward healthcare after an earlier emphasis on financial services. In August 2026, financial services organizations appeared about twice as often as healthcare organizations among targets in its subdomain analysis. Healthcare overtook financial services in September and remained the most targeted industry in October, alongside financial services.

Unit 42 observed Vortex primarily targeting healthcare, pharmaceutical and other medical organizations. Its wider victimology also names legal organizations and other data-rich sectors. This matters because cloud collaboration and patient or research data can increase the pressure created by theft and internal extortion messages.

The geographic measure has a narrower meaning than a victim tally. Australian organizations represented less than 1% of Unit 42’s observed target subdomains in August and September 2026, then about 13% in October. These are shares of observed subdomains, not confirmed compromises, unique organizations, or a measured national attack rate.

For organizations with Australian or healthcare operations, we recommend raising the priority of help desk identity verification and cloud access review. The source describes targeting patterns, so this is our defensive prioritization, not a claim that a particular organization was breached.

Which Checks Separate a Suspected Vortex or Cinder Case?

Start with the employee’s account of any unexpected support call and the sign-in sequence that followed it. Review the time, device, browser, conditional access result and any new MFA registration. A new device shortly after authentication matches a Vortex behavior that Unit 42 observed, but the event needs account-level investigation.

For Cinder-like activity, examine persistent sessions and token reuse after the call. Compare the originating device and network with subsequent access, then review whether MFA was requested again. Unit 42 says Cinder reused an existing session to avoid a fresh Duo prompt; a successful prior challenge alone cannot clear the later activity.

Next, inspect Microsoft 365 mailbox, OneDrive and SharePoint access for unusual reads or exports. Preserve identity, audit and cloud activity records before changing accounts or sessions. Unit 42 observed both clusters taking cloud data and using internal messages for extortion, so investigate these stages together.

Unit 42 also reported a malicious browser extension in a different cluster, CL-CRI-1192. It assessed with moderate confidence that the extension offered another credential theft route for that cluster. Do not assign that extension to Vortex or Cinder based on this report; check extension inventory when the case evidence points to browser misuse.

External impersonation monitoring can help identify organization-specific sign-in lures mentioned in the report. The vishing glossary explains the phone-based entry point, while credential compromise gives the identity context.

What Should Defenders Change First?

Unit 42 recommends tighter help desk verification, phishing-resistant MFA, browser extension allowlists, visibility into identity actions and alerts on unauthorized exports. These controls address different parts of the observed chain. A verification rule reduces the chance that a caller can redirect staff; identity and export monitoring help catch activity after a session has been captured.

Identity and cloud response priorities
  • Help deskRequire an independent callback or approved channel before assisting with account or MFA changes.
  • IdentityAlert on new MFA devices, unusual session reuse and unapproved application consent.
  • Cloud dataReview unusual mailbox, OneDrive and SharePoint reads or exports.
  • BrowserAudit extensions and restrict unapproved installations where policy permits.

Brandefense Blackhole counted 283,108 dark-chat posts matching the broad term “Com” from 23 August through 21 November 2026. That search term can match unrelated discussion, so the count cannot measure these campaigns, unique actors, victims or successful intrusions. Use Unit 42’s dated observations for the campaign-specific decision and treat this broad count only as background discussion volume.

For an immediate response, preserve the call report, revoke suspect sessions, review newly enrolled MFA devices and check recent cloud exports. Test help desk procedures with staff who manage identities across healthcare and Australian operations. These are our recommended steps based on Unit 42’s chain, not a statement that all affected organizations saw every behavior.

Frequently Asked Questions

Are Vortex and Cinder the same as Bling Libra?

Unit 42 lists Vortex and Cinder as separate activity clusters within broader Com-affiliated activity. It lists Bling Libra separately.

Does the October 13% figure count Australian victims?

No. Unit 42 reports Australian organizations in about 13% of observed target subdomains in October 2026. It does not present that share as confirmed compromises.

What should a team check after a suspicious help desk call?

Review new MFA registrations, persistent sessions, cloud data access and internal extortion messages. Preserve logs before revoking suspect sessions and changing credentials.

Sources

  1. Unit 42, Dialing for Data: Inside the Com’s High-Profile Heists, 20 November 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →