TL;DR: A fake Microsoft Teams IT support scam likely delivered the SNOWBELT browser extension backdoor, with a dropped executable, AutoHotKey script execution, and post-install reconnaissance aimed at domain administrators and LDAP services, according to Blackpoint Cyber research. The pattern shows why collaboration-tool trust, extension allowlisting, and script controls now matter as much as email filtering.
Editorial analysis by NHI Mgmt Group, based on content published by Blackpoint Cyber: “Blackpoint SOC Threat Pulse: Week of 10/5”.
Key questions
Q: What fails when users can install browser extensions through trusted collaboration channels?
A: The failure is trust amplification.
Q: Why do support scams inside collaboration tools increase privilege risk?
A: They move the attacker closer to identity discovery without triggering the same scrutiny as external phishing.
Q: What signs show that a malicious extension installation is moving toward escalation?
A: Look for a chain that starts with file staging or script execution and is followed by LDAP enumeration, domain administrator discovery, or other directory-service probing.
Practitioner guidance
- Restrict collaboration-tool messaging paths Block or require approval for chats from external or unverified tenants, and monitor for unsolicited IT support claims that ask users to run scripts or install fixes.
- Enforce browser-extension allowlisting Allow only approved Chromium extensions and review any sideloaded or user-installed extension against a documented business need and owner.
- Limit local script execution Disable or tightly restrict AutoHotKey and similar scripting engines on endpoints that do not require them, and log attempts to launch scripted installers.
Bottom line: This incident shows how a trusted collaboration channel, a local script, and a browser extension can combine into a workable access chain.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →