Security

MacSync Stealer Hunting: New Behavioral Detection

3 min read

Summary

Microsoft Defender Experts detailed how defenders can track MacSync Stealer on macOS by focusing on recurring behaviors instead of fast-changing domains. The research links more than 30 related domains and shows how process, command-line, and network telemetry can reveal payload delivery, staging, and chunked data exfiltration.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new research on MacSync Stealer, a macOS-focused infostealer that rapidly rotates its infrastructure to evade traditional domain-based detection. For security teams, the key takeaway is clear: static IOC blocking is not enough when attackers frequently swap domains, but consistent behaviors across execution, network traffic, and exfiltration can still provide reliable detection opportunities.

What’s new

Microsoft Defender Experts expanded prior public reporting by using behavioral pivots to connect MacSync Stealer activity across changing infrastructure.

Key findings

  • Microsoft linked more than 30 domains to MacSync Stealer activity.
  • The malware used recurring URI paths such as /curl/, /dynamic?txd=, and /gate?buildtxd=.
  • Requests consistently included macOS User-Agent strings, API-key headers, and specific curl options like -k, -s, --max-time, and --data-binary.
  • Researchers confirmed active exfiltration, not just C2 beaconing.
  • Stolen data was staged in temporary paths, compressed, split into chunks, and uploaded with HTTP PUT requests using parameters such as upload_id, chunk_index, and total_chunks.

Attack chain overview

The observed attack chain starts with ClickFix-style social engineering, where a user is tricked into pasting or running commands in Terminal. From there:

  • curl retrieves the payload from attacker infrastructure.
  • Native tools like base64 and gunzip help decode or unpack content.
  • osascript is used to drive AppleScript-assisted execution.
  • The malware collects Keychain data, browser information, SSH credentials, cloud credentials, and sensitive user files.
  • Collected data is archived and uploaded in chunks over rotating infrastructure.
  • Temporary artifacts are removed to reduce forensic evidence.

Why this matters for administrators

For SOC analysts and IT administrators managing macOS fleets, this research reinforces the value of behavior-based hunting. Domain indicators may expire quickly, but repeated execution patterns and request shapes often persist longer.

Defenders should prioritize correlation across:

  • Shell ancestry and interactive zsh sessions
  • Suspicious curl command lines
  • osascript launching shell activity
  • Archive creation in temporary directories
  • Outbound HTTP PUT uploads with chunking parameters
  • Review detections for interactive Terminal-driven payload execution on managed Macs.
  • Hunt for curl activity tied to the URI patterns and upload parameters Microsoft identified.
  • Monitor for temporary archive creation followed by outbound uploads.
  • Ensure Microsoft Defender for Endpoint or equivalent macOS telemetry is enabled and centrally reviewed.
  • Educate users about ClickFix and terminal-based social engineering techniques.

Microsoft’s analysis is a strong reminder that durable detections come from understanding attacker behavior, not just blocking the latest domain list.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

MacSync StealermacOS securityMicrosoft Defenderthreat huntingdata exfiltration

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.