Productivity & Comms Apps · Productivity/Comms · Data breach
Microsoft Teams
Headline
Microsoft's own Incident Response team documented attackers using Teams itself as the delivery mechanism - impersonating IT help desk staff in chat and voice calls to talk employees into granting access.
Not independently verified. Verification status: Unverified - heuristic first draft. Publish state: draft unverified.
Microsoft's own Incident Response team documented attackers using Teams itself as the delivery mechanism - impersonating IT help desk staff in chat and voice calls to talk employees into granting access. That is the finding worth generalising: the security control most organisations rely on is 'the message came through our internal, authenticated corporate tool,' and the attack works precisely because that assumption is doing all the work. This is the same social-engineering pattern that produced the Aflac breach documented in Life-Health-Dental and the broader 2025-26 campaign this tracker treats as its biggest connective thread. No technical exploit is involved.
- Severity
- Evidence tierUnassigned
- Claims confirmed
- Last verified2026-08-04
Primary source. None recorded — Unverified - heuristic first draft.
Terms
Arbitration
Not independently confirmed this pass — governed by Microsoft's overall Services Agreement (see Microsoft/Outlook row, Consumer Apps tab).
Data sharing
REPEATED SOCIAL-ENGINEERING ATTACK VECTOR (2025-2026): Microsoft's own Incident Response team (DART) documented multiple campaigns using Teams specifically as an entry point — attackers impersonating IT support staff via TEAMS VOICE PHISHING ('vishing') convinced employees to grant remote access through Quick Assist, leading to full corporate-device compromise (Nov 2025 case). Separately, Rapid7 reported (May 2026) an early-2026 intrusion it attributed with moderate confidence to the Iranian state-linked MuddyWater group: the attacker sent unsolicited external Teams chat requests, then used interactive screen-sharing to get employees to type credentials into local text files and add attacker-controlled devices to their MFA, while disguising the operation as Chaos ransomware. Microsoft has also reportedly tightened Teams default security settings (not independently verified this pass).
Fees and billing
SEPARATE FEATURE-LEVEL CONCERN (Microsoft 365 message center MC1182004): a Teams feature, enabled by default, lets users start chats with anyone with an email address, including non-Teams users who join as guests (targeted release November 2025; worldwide general availability from January 2026) — cybersecurity commentators warned this significantly expands the phishing/malware attack surface, comparing the default-enabled risk to oversights that contributed to the SolarWinds breach; administrators can disable it by setting UseB2BInvitesToAddExternalUsers in TeamsMessagingPolicy to false via PowerShell, but many organizations may not realize they need to.
Contacts
Privacy contact. No published privacy email; Microsoft routes requests via microsoft.com/concern/privacy (30-day response commitment)
Legal notice. PUBLIC COMPANY (MSFT). Service route: c/o General Counsel / Corporate Secretary, Redmond, Washington — the corporate address on the SEC Form 10-K cover page is the official address of record. Confirm the exact street address on the current 10-K at sec.gov/edgar, and check the state-of-incorporation registered agent (usually Delaware; most large filers use The Corporation Trust Company or Corporation Service Company) via the Secretary of State business-entity search. A registered agent MUST accept service, which is why it is the reliable channel when a company publishes no privacy address.
Mailing address. Microsoft Corporation, One Microsoft Way, Redmond, WA 98052-6399, USA
Evidence
No claims have been itemized for this row yet.
No sources are on file for this row yet.
Source vault
Link status: Candidate - not yet fetched
| Document | Last fetch | |
|---|---|---|
| Privacy policy privacy.microsoft.com/en-us/privacystatement | Not fetched yet | NO (HTML only) |
| Terms of service microsoft.com/en-us/servicesagreement/ (governed by Microsoft's overall Services Agreement) | Not fetched yet | NO (HTML only) |
| Website microsoft.com | Not fetched yet | — |
| Primary source No URL recorded Verification: Unverified - heuristic first draft | Not fetched yet | — |
Enforcement
No enforcement actions are linked to this row.
State statute
No comprehensive state privacy statute on file for Washington