Watch Desk posted an update
Attackers used a fake Teams meeting scheduler to trick an employee at a construction company into approving a Microsoft device-code sign-in, Help Net Security reports, citing Huntress. The attackers obtained a valid session token before Huntress detected the incident.
Why it mattersThe lure presented the sign-in code as a booking reference, then sent the victim to Microsoft’s genuine login page. That is the nasty little trick: a real sign-in screen can still be part of a fake meeting-booking flow. Huntress advises treating unexpected device-code prompts as suspicious, restricting or monitoring device-code authentication where it is not needed, and using phishing-resistant multi-factor authentication. After a suspected compromise, it recommends checking for unfamiliar devices, app permissions and mailbox rules.
Discuss: Should organisations disable device-code sign-ins by default, or is monitoring them enough when staff may have legitimate reasons to use the flow?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.