Threat actors distributing the Atomic Stealer (AMOS) infostealer have adapted their tactics to bypass recent security enhancements in macOS. According to researchers at Jamf Threat Labs, a new campaign is using an evolved version of the "ClickFix" social engineering attack. Instead of tricking users into pasting malicious commands into the Terminal, which now triggers a security warning in macOS 26.4, the attackers now guide victims to use Apple's built-in Script Editor. This demonstrates the continuous cat-and-mouse game between platform vendors and malware authors, where attackers quickly find alternative paths to achieve their goals once a vector is closed.
Atomic Stealer is a potent infostealer designed specifically to target macOS, capable of harvesting a wide range of sensitive data, including browser passwords, cookies, crypto wallets, and system information. The "ClickFix" attack is a social engineering method that relies on deception rather than a software vulnerability.
The new attack chain is as follows:
This campaign is a clear example of attackers adapting to new defenses. Apple's introduction of a warning for pasting commands into the Terminal in macOS 26.4 was a meaningful security improvement. However, the attackers simply pivoted to another built-in application that can execute code.
T1204.001 - User Execution: Malicious Link and T1204.002 - User Execution: Malicious File, as the user is the one who ultimately executes the code.do shell script command. This allows the attacker to execute arbitrary shell commands to download and run the main AMOS binary, a technique covered under T1059.002 - Command and Scripting Interpreter: AppleScript.A successful infection with Atomic Stealer can lead to a complete compromise of the victim's digital life and credentials.
No specific IOCs were provided in the summary articles.
Detection relies on monitoring for the execution of suspicious scripts and outbound network connections.
osascript process). Look for scripts that make outbound network connections or write files to disk.osascript execution and file creation in suspicious directories like /tmp/ or ~/Library/LaunchAgents/.D3FEND Reference: Detection would involve D3-PA - Process Analysis to watch for osascript spawning shell processes that download files, and D3-NTA - Network Traffic Analysis to spot the C2 communication.
Since this is a social engineering attack, user awareness is the primary mitigation.
D3FEND Reference: The most effective countermeasure is user-focused. While not a direct D3FEND technique, this aligns with the principle of hardening the human element. Technically, D3-EDL - Executable Denylisting could be used to block Script Editor for most users, but this is often not practical.
The most effective mitigation is training users to recognize the social engineering tactic and to never copy/paste code from an untrusted source into any application.
Deploy a reputable EDR/EPP solution for macOS that can detect and block Atomic Stealer and its behaviors.
To counter the evolved 'ClickFix' attack, defenders should use Process Analysis to monitor for the specific, anomalous behavior of the Apple Script Editor. A key detection rule would be to alert whenever the Script Editor's underlying process, osascript, executes a 'do shell script' command that involves network activity, such as curl or wget. This is a very strong indicator of a malicious script attempting to download a second-stage payload. Furthermore, an EDR solution should be configured to analyze the chain of events: Browser -> User launches Script Editor -> Script Editor process (osascript) spawns a shell -> Shell process makes a network connection. This behavioral chain is highly indicative of the AMOS campaign and allows for detection regardless of the specific script or payload hash.
Since this attack relies on abusing a legitimate, built-in macOS application, a powerful mitigation for corporate environments is to use Executable Denylisting. Most non-developer users have no legitimate reason to use the Apple Script Editor. Using an MDM solution or EDR platform, administrators can create a policy that prevents the execution of Script Editor.app for all users except those in a specific 'developer' group. This directly removes the tool that the attackers have pivoted to, forcing them to find yet another vector. While this may seem like a blunt instrument, it's an effective way to harden endpoints and reduce the attack surface by removing unnecessary, dual-use tools from standard user machines.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats