ctipilot.ch

MacSync

malware · malware:macsync single-source

Six-stage macOS infostealer and remote-access tool analysed by Huntress, delivered through a sponsored search result leading to a publicly shared conversation page on the genuine claude.ai domain that instructs the victim to paste a curl one-liner into Terminal. Stages run a polymorphic zsh loader in memory, a server-side AppleScript stealer, a Mach-O remote-access tool persisting via a launch agent, a helper for the screen-recording permission and a set of wallet-application trojans; collection covers browser cookies and logins, keychain secrets, Telegram sessions, SSH and cloud keys (Huntress, 2026-08-17).

Coverage timeline
3
first 2026-07-14 → last 2026-08-23
Peak priority
high
1 high · 2 notable
Sources cited
5
5 hosts
Sections touched
2
active-threats, weekly-research
Co-occurring entities
3
see Related entities below
ATT&CK techniques
24
pinned v19.2 · see below

ATT&CK techniques

24 techniques observed across 3 entries — derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Resource Development TA0042

T1608.004Stage Capabilities: Drive-by Target×1

Adversaries may prepare an operational environment to infect systems that visit a website over the normal course of browsing. Endpoint systems may be compromised through browsing to adversary controlled sites, as in Drive-by Compromise. In such cases, the user's web browser is typically targeted for exploitation (often not requiring any extra user interaction once landing on the site), but adversaries may also set up websites for non-exploitation behavior such as Application Access Token. Prior to Drive-by Compromise, adversaries must stage resources needed to deliver that exploit to users who browse to an adversary controlled site. Drive-by content can be staged on adversary controlled infrastructure that has been acquired (Acquire Infrastructure) or previously compromised (Compromise Infrastructure).

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

Initial Access TA0001

T1189Drive-by Compromise×1

Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. Multiple ways of delivering exploit code to a browser exist (i.e., Drive-by Target), including:

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

Execution TA0002

T1059.001Command and Scripting Interpreter: PowerShell×1

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · ATT&CK page ↗

T1059.004Command and Scripting Interpreter: Unix Shell×2

Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

T1204.002User Execution: Malicious File×1

An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, .cpl, .reg, and .iso.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1204.004User Execution: Malicious Copy and Paste×2

An adversary may rely upon a user copying and pasting code in order to gain execution. Users may be subjected to social engineering to get them to copy and paste code directly into a Command and Scripting Interpreter. One such strategy is "ClickFix," in which adversaries present users with seemingly helpful solutions—such as prompts to fix errors or complete CAPTCHAs—that instead instruct the user to copy and paste malicious code.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

Persistence TA0003

T1176.001Software Extensions: Browser Extensions×1

Adversaries may abuse internet browser extensions to establish persistent access to victim systems. Browser extensions or plugins are small programs that can add functionality to and customize aspects of internet browsers. They can be installed directly via a local file or custom URL or through a browser's app store - an official online platform where users can browse, install, and manage extensions for a specific web browser. Extensions generally inherit the web browser's permissions previously granted.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · ATT&CK page ↗

T1543.001Create or Modify System Process: Launch Agent×2

Adversaries may create or modify launch agents to repeatedly execute malicious payloads as part of persistence. When a user logs in, a per-user launchd process is started which loads the parameters for each launch-on-demand user agent from the property list (.plist) file found in <code>/System/Library/LaunchAgents</code>, <code>/Library/LaunchAgents</code>, and <code>~/Library/LaunchAgents</code>. Property list files use the <code>Label</code>, <code>ProgramArguments </code>, and <code>RunAtLoad</code> keys to identify the Launch Agent's name, executable location, and execution time. Launch Agents are often installed to perform updates to programs, launch user specified programs at login, or to conduct other developer tasks.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Privilege Escalation TA0004

T1543.001Create or Modify System Process: Launch Agent×2

Adversaries may create or modify launch agents to repeatedly execute malicious payloads as part of persistence. When a user logs in, a per-user launchd process is started which loads the parameters for each launch-on-demand user agent from the property list (.plist) file found in <code>/System/Library/LaunchAgents</code>, <code>/Library/LaunchAgents</code>, and <code>~/Library/LaunchAgents</code>. Property list files use the <code>Label</code>, <code>ProgramArguments </code>, and <code>RunAtLoad</code> keys to identify the Launch Agent's name, executable location, and execution time. Launch Agents are often installed to perform updates to programs, launch user specified programs at login, or to conduct other developer tasks.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Stealth TA0005

T1027Obfuscated Files or Information×2

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1070.006Indicator Removal: Timestomp×1

Adversaries may modify file time attributes to hide new files or changes to existing files. Timestomping is a technique that modifies the timestamps of a file (the modify, access, create, and change times), often to mimic files that are in the same folder and blend malicious files with legitimate files.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1140Deobfuscate/Decode Files or Information×1

Adversaries may use Obfuscated Files or Information to hide artifacts of an intrusion from analysis. They may require separate mechanisms to decode or deobfuscate that information depending on how they intend to use it. Methods for doing that include built-in functionality of malware or by using utilities present on the system.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1218.005System Binary Proxy Execution: Mshta×1

Adversaries may abuse mshta.exe to proxy execution of malicious .hta files and Javascript or VBScript through a trusted Windows utility. There are several examples of different types of threats leveraging mshta.exe during initial compromise and for execution of code

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · ATT&CK page ↗

T1497.001Virtualization/Sandbox Evasion: System Checks×1

Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

T1564.001Hide Artifacts: Hidden Files and Directories×1

Adversaries may set files and directories to be hidden to evade detection mechanisms. To prevent normal users from accidentally changing special files on a system, most operating systems have the concept of a ‘hidden’ file. These files don’t show up when a user browses the file system with a GUI or when using normal commands on the command line. Users must explicitly ask to show the hidden files either via a series of Graphical User Interface (GUI) prompts or with command line switches (<code>dir /a</code> for Windows and <code>ls –a</code> for Linux and macOS).

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1622Debugger Evasion×1

Adversaries may employ various means to detect and avoid debuggers. Debuggers are typically used by defenders to trace and/or analyze the execution of potential malware payloads.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Defense Impairment TA0112

T1553.001Subvert Trust Controls: Gatekeeper Bypass×1

Adversaries may modify file attributes and subvert Gatekeeper functionality to evade user prompts and execute untrusted programs. Gatekeeper is a set of technologies that act as layer of Apple’s security model to ensure only trusted applications are executed on a host. Gatekeeper was built on top of File Quarantine in Snow Leopard (10.6, 2009) and has grown to include Code Signing, security policy compliance, Notarization, and more. Gatekeeper also treats applications running for the first time differently than reopened applications.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Credential Access TA0006

T1552.001Unsecured Credentials: Credentials In Files×1

Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

T1555.001Credentials from Password Stores: Keychain×2

Adversaries may acquire credentials from Keychain. Keychain (or Keychain Services) is the macOS credential management system that stores account names, passwords, private keys, certificates, sensitive application data, payment data, and secure notes. There are three types of Keychains: Login Keychain, System Keychain, and Local Items (iCloud) Keychain. The default Keychain is the Login Keychain, which stores user passwords and information. The System Keychain stores items accessed by the operating system, such as items shared among users on a host. The Local Items (iCloud) Keychain is used for items synced with Apple’s iCloud service.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1555.003Credentials from Password Stores: Credentials from Web Browsers×2

Adversaries may acquire credentials from web browsers by reading files specific to the target browser. Web browsers commonly save credentials such as website usernames and passwords so that they do not need to be entered manually in the future. Web browsers typically store the credentials in an encrypted format within a credential store; however, methods exist to extract plaintext credentials from web browsers.

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Discovery TA0007

T1497.001Virtualization/Sandbox Evasion: System Checks×1

Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · ATT&CK page ↗

T1518.001Software Discovery: Security Software Discovery×1

Adversaries may attempt to get a listing of security software, configurations, defensive tools, and sensors that are installed on a system or in a cloud environment. This may include things such as cloud monitoring agents and anti-virus. Adversaries may use the information from Security Software Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

T1622Debugger Evasion×1

Adversaries may employ various means to detect and avoid debuggers. Debuggers are typically used by defenders to trace and/or analyze the execution of potential malware payloads.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Collection TA0009

T1560.001Archive Collected Data: Archive via Utility×1

Adversaries may use utilities to compress and/or encrypt collected data prior to exfiltration. Many utilities include functionalities to compress, encrypt, or otherwise package data into a format that is easier/more secure to transport.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Command and Control TA0011

T1071.001Application Layer Protocol: Web Protocols×1

Adversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-08-23/weekly-w34-searching-for-an-ai-tool-is-now-an-access-vector · ATT&CK page ↗

T1105Ingress Tool Transfer×2

Adversaries may transfer tools or other files from an external system into a compromised environment. Tools or files may be copied from an external adversary-controlled system to the victim network through the command and control channel or through alternate protocols such as ftp. Once present, adversaries may also transfer/spread tools between victim devices within a compromised environment (i.e. Lateral Tool Transfer).

Evidence: 2026-08-07/macos-clickfix-server-side-fingerprinting-gate-amos · 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Exfiltration TA0010

T1041Exfiltration Over C2 Channel×1

Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.

Evidence: 2026-07-14/crashstealer-macos-native-cpp-infostealer · ATT&CK page ↗

Story timeline

  1. 2026-08-23Two vendors independently published in the same week on the same delivery chain — an employee searches for an AI coding assistant, clicks a sponsored result, and pastes a one-liner into a terminal — and in one case the page hosting the instructions was on the vendor's own genuine domain
    weekly-researchA year of managed-detection casework says impersonating an AI brand is the dominant AI-related threat, ahead of anything AI actually does
  2. 2026-08-07The macOS ClickFix chain now qualifies visitors server-side before showing the lure, with anti-analysis probes that detect a console rather than a sandbox
    active-threatsMicrosoft documents the cloaking layer in front of a ClickFix campaign — researchers and scanners get a decoy, qualified Macs get the payload
  3. 2026-07-14CrashStealer — a native-C++ macOS infostealer using a notarized dropper and local dscl password validation to raid keychain, browsers and wallets
    active-threatsCrashStealer: notarized-dropper macOS stealer validates stolen passwords with dscl before harvesting keychain and browser data

Where this entity is cited

  • active-threats2
  • weekly-research1

Source distribution

  • bleepingcomputer.com1 (20%)
  • huntress.com1 (20%)
  • jamf.com1 (20%)
  • microsoft.com1 (20%)
  • sophos.com1 (20%)

Co-occurring entities

Derived — referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Entries about MacSync (3)

2026-08-23 · view entry permalink →

HIGHNATOB1

Two vendors independently published in the same week on the same delivery chain — an employee searches for an AI coding assistant, clicks a sponsored result, and pastes a one-liner into a terminal — and in one case the page hosting the instructions was on the vendor's own genuine domain

Two managed-detection providers published on the same delivery chain two days apart this week, from separate telemetry, without citing each other. That convergence is the reason this belongs in a strategic view rather than in either day's operational coverage: it moves "employees searching for AI tools get malware" from an anecdote to a measured, cross-vendor initial-access vector.

Sophos X-Ops supplies the measurement. Reviewing twelve months of managed-detection casework from 2 July 2025 to 29 June 2026, it tagged 86 cases for AI involvement, confirmed 34 on individual review against its own taxonomy, added four found through analyst investigation, and worked from the resulting 38. Of those, AI software impersonation accounted for 30, and the Claude brand was the most frequently abused lure at 26 of the cases reviewed (Sophos X-Ops, 2026-08-19). Its framing of the finding is the headline result: "Attackers are exploiting the surge in demand for AI software by faking the software itself: names users trust, like Claude, ChatGPT, and Copilot, become delivery vehicles for malware." The typical chain is a user searching for an AI coding tool, landing on a typosquatted site through a malicious ad, and being walked through an "InstallFix" pretext — a variant of ClickFix in which the cover story is software installation — into running an obfuscated one-liner. In one case a fake Claude site instructed the victim to run an mshta one-liner, followed by a PowerShell download-and-execute one-liner running code in memory. The most developed example Sophos observed outside its own casework was a fake Claude site that delivered a DLL-sideloading chain ending in a backdoor Sophos names Beagle — which is the same name it gave a fake-Claude DLL-sideloading backdoor documented in May 2026 and already carried in this store. A parallel vector runs through browser extensions impersonating AI assistants — one marketed as an AI sidebar bundling several assistant brands — which functioned as infostealers.

Two findings from Sophos are worth separating from the alarm. First, its verdict on detection: in the impersonation cases it reviewed, the decisive protections were conventional delivery- and payload-behaviour detections rather than anything AI-specific. Second, and more useful for scoping: of the 38 cases, 35 fall under malicious targeting of AI — abuse of AI products, brands and ecosystems — rather than under attackers wielding AI as a capability. For a defender deciding where to spend attention on "AI threats", a year of casework says the brand is the exposure, not the model.

Huntress's case removes the step everyone's guidance depends on. Its MacSync analysis describes a victim searching "How to Install Claude on a Mac", clicking a sponsored Google Ads result, and being taken to Anthropic's genuine claude.ai domain — to a publicly shared conversation page rather than the official install guide, carrying a badge showing it had been shared under the display name "Apple Support", with the page instructing the reader to paste a curl one-liner into Terminal (Huntress, 2026-08-17). Every control that keys on the destination passes: the domain is real, the certificate is the vendor's, there is no typosquat to catch, and standard user guidance — "check you are on the vendor's real site" — returns the wrong answer.

The chain behind it is six stages and worth knowing in outline because each one is a different telemetry class. The initial curl returns a 1,442-byte zsh loader, a three-line wrapper around a gzip-compressed, Base64-encoded payload; because the wrapper is polymorphic, each build differs by the victim token the attacker issues. One Huntress analyst's conclusion is the operational summary: "you can't detect based on the hash, you're gonna have to detect on the behavior." Stage two runs a background zsh function in memory; stage three is a server-side AppleScript stealer that keeps the valuable logic off the endpoint behind an API-key gate; stage four installs a Mach-O remote-access tool that builds a property list and triggers a launch agent named after an updater already present on the host, giving persistence across logins; a separately signed helper exists to obtain a single screen-recording permission; and a set of wallet-application trojans completes it. The collection covers browser cookies and logins, keychain secrets, account passwords, Telegram sessions, SSH keys and cloud keys, alongside three trojanised hardware-wallet companion applications phishing for recovery phrases — of which Huntress notes the property that makes that last category different in kind: "A recovery phrase doesn't work like that; there is nothing to revoke or reset, nothing to stop the access."

Attackers are exploiting the surge in demand for AI software by faking the software itself: names users trust, like Claude, ChatGPT, and Copilot, become delivery vehicles for malware.

Sophos X-Ops 2026-08-19

you can't detect based on the hash, you're gonna have to detect on the behavior.

A recovery phrase doesn't work like that; there is nothing to revoke or reset, nothing to stop the access.

Huntress 2026-08-17
research23 Aug 23:57Zmulti-sourceOpen finding ↗

2026-08-07 · view entry permalink →

NOTABLENATOB2

The macOS ClickFix chain now qualifies visitors server-side before showing the lure, with anti-analysis probes that detect a console rather than a sandbox

The interesting part of this campaign is no longer the lure but the doorway in front of it. Microsoft Threat Intelligence reports that the macOS ClickFix activity it has been tracking now performs visitor qualification on the server before it will show anything malicious: "Rather than immediately presenting a malicious command, the actor performs server-side victim qualification before revealing the lure, reducing visibility to researchers and automated security systems while maintaining access to intended macOS targets" (Microsoft Threat Intelligence, 2026-08-05). The gate is hosted across a large set of algorithmically generated domains — Microsoft "confirmed more than 250 ClickFix front-end domains during the tracking window, and many followed a repeated naming pattern using the token “file” with dictionary-style words", i.e. a file<word><word> construction — and the decision is not made in the browser where an analyst could read it — "the gate profiles each visitor using a combination of browser, hardware, and runtime attributes, which are submitted to the server for evaluation" (Microsoft Threat Intelligence, 2026-08-05). A visitor that fails qualification receives a decoy page or nothing at all, which is why a scanner's verdict on one of these URLs is close to worthless.

The profiling itself is broader than the usual sandbox checks. Microsoft describes collection across the browser's navigator, screen, window, document, location and console objects, a WebGL query for genuine graphics hardware, and environmental signals including timezone, iframe presence and touch-input support. Two probes stand out because they target the analyst rather than the machine. The first is a counter driven by JavaScript's own string coercion: "the script creates a temporary function whose toString() method increases a counter, then writes that function to the console" (Microsoft Threat Intelligence, 2026-08-05). In a normal browser that counter usually stays put, because nothing serialises the function; if the developer console is open, or a headless or log-capturing tool serialises console output, the function gets converted to a string and the counter moves. The check does not ask "am I in a VM?" — it asks "is somebody reading this page's console?", which a well-built analysis harness answers in the affirmative precisely because it is instrumented. The second is prototype-tampering detection, which catches the hooking that instrumentation frameworks rely on.

A qualified visitor is served a counterfeit page presenting a "Verified Publisher" framing and a Download for macOS action carrying an obfuscated curl one-liner, in the ClickFix pattern of getting the user to paste and run a command themselves. That command retrieves a staged script from a structured path on the operator's infrastructure, and the chain ends in an infostealer — Microsoft names MacSync and Atomic Stealer (AMOS) as the families delivered — collecting credentials, browser data and cryptocurrency-wallet contents (Microsoft Threat Intelligence, 2026-08-05).

Rather than immediately presenting a malicious command, the actor performs server-side victim qualification before revealing the lure, reducing visibility to researchers and automated security systems while maintaining access to intended macOS targets.

The gate profiles each visitor using a combination of browser, hardware, and runtime attributes, which are submitted to the server for evaluation.

The script creates a temporary function whose toString() method increases a counter, then writes that function to the console.

On macOS 26.4 and later, Apple introduced a mitigation that displays a warning when a user attempts to paste a potentially malicious command into Terminal, directly addressing the ClickFix delivery mechanism.

Where feasible, alert the file<word><word> domain pattern rather than maintaining a list of individual domains.

Microsoft Threat Intelligence 2026-08-05
threat07 Aug 04:41Zsingle-sourceOpen finding ↗

2026-07-14 · view entry permalink →

NOTABLENATOB2

CrashStealer — a native-C++ macOS infostealer using a notarized dropper and local dscl password validation to raid keychain, browsers and wallets

Jamf Threat Labs documents CrashStealer, a macOS infostealer written in native C++ (around an internal MacOSData class) rather than the AppleScript droppers or thin Objective-C wrappers typical of commodity macOS stealers; Jamf first saw a sample on VirusTotal in early May 2026 and observed in-the-wild payload detections by early July, and tracks it as a distinct family rather than a variant of Atomic (AMOS), MacSync or Phexia (Jamf Threat Labs, 2026-07-13; BleepingComputer, 2026-07-13). Initial access is a signed and Apple-notarized dropper distributed as a "Werkbit Setup" disk image (both the image and the inner app are signed under a valid Developer ID — which Jamf reported to Apple after confirming it was used to distribute malicious payloads — with hardened runtime enabled) — because it carries a valid notarization ticket it clears Gatekeeper on first launch, so the "right-click → Open" instruction the installer shows is pure social engineering rather than a technical bypass (Jamf Threat Labs, 2026-07-13). The dropper fetches a first-stage file from a GitHub repository (keeping the opening network hop on a trusted developer domain), decodes a curl command, and pulls a shell script delivered as successive Base64 blobs decoded at runtime and piped to bash; that script downloads the payload disk image, copies the app into a hidden /private/tmp/.CrashReporter directory, strips and re-signs it ad-hoc (codesign --remove-signature then codesign -s - --force --deep), registers it with Launch Services and launches it (Jamf Threat Labs, 2026-07-13).

The payload impersonates Apple's crash reporter (bundle identifier com.apple.crashreporter, executing from the hidden staging path), clears its own quarantine and last-used-date extended attributes with xattr -cr, then presents a native-styled password prompt and validates the entered credential locally with dscl . -authonly, looping until a valid password is supplied — so the operator only ever collects credentials that actually authenticate (Jamf Threat Labs, 2026-07-13). With the validated password it unlocks the login keychain, copies login.keychain-db into a hidden ~/.cache staging root, runs a reconnaissance sweep (defaults read for version paired with du -sh for on-disk size) against an embedded list skewed toward malware-analysis and EDR tooling to profile the defensive environment, and collects browser data, Chromium/Firefox extensions (including cryptocurrency-wallet extensions) and password-manager material — AES-GCM-encrypting each item into hidden staging files as it is collected (so the loot is never written to disk in the clear), then packaging each staging directory into its own zip archive before exfiltrating over libcurl. Persistence is a LaunchAgent registered under an Apple-impersonating label with a second re-signed copy of the binary. Anti-analysis is layered throughout: the binary checks for an attached debugger via sysctl process-flag (P_TRACED) inspection at two separate points in initialization — so patching out the first check alone does not defeat it — and its C2 address and collection-target list are held as encrypted, runtime-decoded strings behind control-flow-flattening obfuscation rather than in cleartext (Jamf Threat Labs, 2026-07-13).

Validating the password with dscl -authonly before harvesting lets the operator keep only credentials that actually work

Patching out that first check is not enough on its own: a second check later in application initialization exits the same way

Jamf Threat Labs 2026-07-13
threat14 Jul 04:35Zmulti-sourceOpen finding ↗