Back to the blog

AmnesiaStealer on Mac: protect enterprise Apple fleets

Article created on August 19, 2026 · Source analyzed on August 19, 2026 · Jamf Threat Labs source published on August 13, 2026 · Topic: macOS security, MDM, Jamf and incident response

Jamf Threat Labs observed AmnesiaStealer in the wild: a multi-stage macOS infostealer distributed through a counterfeit GitHub page that tells the user to paste a command into Terminal. For an enterprise, the incident goes beyond downloading a binary. It combines social engineering, the login password, keychains, browser data and hijacked authenticated sessions.

1. An attack chain that exploits user trust

The counterfeit page imitates GitHub and presents a supposed macOS installation. Jamf's analysis says the command retrieves a script and then a universal binary written in Rust. The malware profiles the Mac, requests the password through an installer-like window, collects keychains, Chromium data, Notes and Telegram data, and can then load a module providing hidden browser control.

Jamf also reports that the code attempts bypasses Apple has already patched. They failed under the observed macOS 26 conditions, but this protection does not neutralize what the user authorizes by pasting the command and disclosing a password.

2. Why MDM alone is not enough

A Mac enrolled in Apple Business and managed through MDM remains exposed if the user can execute an unknown chain, retains permanent administrator rights and has no security telemetry. MDM provides inventory, configurations and compliance; prevention also requires software control, web and DNS filtering, endpoint protection and detection capability.

Organizations must focus on sessions too: stolen cookies or Chromium profiles may expose SaaS applications without an immediate password replay. MFA and SSO remain essential, but response procedures must include session revocation, secret rotation and endpoint investigation.

3. What does this change for a Belgian or French company?

For an SME, the first priority is to remove permanent administrator rights when they are not justified and establish a trusted software-distribution channel. For a mid-market organization, large enterprise or public body, the model should add centralized detection, consistent filtering on and off the corporate network, and a process to isolate the Mac quickly.

In Belgium and France, IT teams must also account for GDPR and internal notification duties: potentially collected data includes documents, Notes, credentials, SaaS sessions and personal information. Security, IT, the DPO and business owners should qualify the incident according to the data actually exposed.

4. Underside analysis: connect execution, identity and browser security

Our reading is that this campaign exposes a common blind spot: treating Mac management, identity and browser security as separate domains. An effective policy connects Apple Business, Automated Device Enrollment, Jamf or another MDM, least privilege, execution control, endpoint telemetry, network filtering and SSO revocation procedures.

Teams should not block Terminal indiscriminately. They should distinguish developers who need it, standard users and sensitive workstations, then apply proportionate controls: temporary privilege elevation, allowed software, detection of quarantine-attribute removal, LaunchDaemon monitoring and alerts for unusual command chains.

5. Recommended action plan

Goal: prevent a command copied from a counterfeit page from turning a managed Mac into an access point for identities, browsers and business data.

Assess your Mac fleet security

Official source: Jamf Threat Labs, “AmnesiaStealer: a multi-stage Rust-based macOS infostealer that hijacks Chromium browsers”, published on August 13, 2026. Also read our analysis of Apple declarative app and binary execution control.