Trapdex Subscribe

CampaignsFake support session

UNC6692: email bombing, then a fake helpdesk on Teams sends a "spam patch" that installs the SNOW malware suite

Do this now

  1. Restrict Teams external access to allowed domains; tell staff the helpdesk never sends a 'patch' link in chat
  2. Block browser extensions installed from outside the managed store (extension allow-list by policy)
  3. Alert on AutoHotkey running from a user download folder and on headless Edge scheduled tasks
  4. Turn on Credential Guard and alert on LSASS memory access

Indicators

For blocklists and log searches. All values are defanged.

  • domain4
  • sha2566

CSVJSONAll 10 indicators

What happened

After an email bombing campaign, UNC6692 messaged employees on Microsoft Teams as helpdesk staff offering help with the flood, and sent a link to a fake 'Mailbox Repair and Sync Utility' page. The 'local patch' it served ran an AutoHotkey script that installed a malicious Chromium extension (SNOWBELT), a tunneler (SNOWGLAZE) and a bind shell (SNOWBASIN). The intrusion moved on to credential dumping and domain controller compromise.

  • Microsoft Teams
  • Email
  • Windows

Attack chain

  1. Lure

    Email flood, then a Teams message from 'helpdesk personnel' offering to help with the email volume

    First seen

  2. Artifact

    'Microsoft Spam Filter Updates' patch from a fake mailbox repair page: an AutoHotkey script that installs the SNOWBELT browser extension, SNOWGLAZE and SNOWBASIN

    Legitimate software

    AutoHotkey is legitimate software and is not malware. In this campaign the attacker's malicious code installed it and set it up for the attacker; the malicious part is that code and the access it gave the attacker.

  3. Actor

    UNC6692

  4. Infrastructure

    • Payload pages and downloads on attacker-created AWS S3 buckets
    • WebSocket C2 on Heroku

    Last seen

What the attacker installed afterwards

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
domaincloudfront-021[.]s3[.]us-west-2[.]amazonaws[.]com
domainsad4w7h913-b4a57f9c36eb[.]herokuapp[.]com
domainservice-page-25144-30466-outlook[.]s3[.]us-west-2[.]amazonaws[.]com
domainservice-page-11369-28315-outlook[.]s3[.]us-west-2[.]amazonaws[.]com
sha2562fa987b9ed6ec6d09c7451abd994249dfaba1c5a7da1c22b8407c461e62f7e49
sha256c8940de8cb917abe158a826a1d08f1083af517351d01642e6c7f324d0bba1eb8
sha2567f1d71e1e079f3244a69205588d504ed830d4c473747bb1b5c520634cc5a2477
sha256ca390b86793922555c84abc3b34406da2899382c617f9dcf83a74ac09dd18190
sha2566e6dab993f99505646051d2772701e3c4740096ff9be63c92713bcb7fcddf9f7
sha256de200b79ad2bd9db37baeba5e4d183498d450494c71c8929433681e848c3807f

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • Actor: UNC6692 (attribution: Google GTIG/Mandiant; basis: their incident response and malware analysis). GTIG links it to no other named group.
  • first_seen is GTIG's 'late December 2025' email campaign; last_seen is the report date.
  • AutoHotkey is a legitimate scripting tool; the malicious parts are the script and the SNOW components. Hashes are SNOWGLAZE, SNOWBASIN and four SNOWBELT extension files (background.js, dream.js, dream.html, helper.html).
  • SNOWBELT is a browser extension, so this entry is also relevant to browser-extension.
  • The S3 and Heroku names are attacker-created resources on shared platforms; don't block the parent services.
  • The two service-page S3 bucket hostnames are from GTIG's indicator list. One hosted the phishing page and the first AutoHotkey payloads; the other received an uploaded text file. They are attacker-created buckets on a shared service.
  • All six hashes verified byte-exact against the raw GTIG page on 16 Nov 2026. GTIG lists no other file hashes; its DGA seed is not a file hash.
  • Status re-checked 16 Nov 2026 against the GTIG page (published 23 Apr 2026, no later update); no takedown reported, so status stays unknown.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.