Fake Zoom Mac Installer Skips Gatekeeper, Steals Data

What Happened: A Fake Zoom Installer on macOS

Jamf, a leading provider of Apple‑focused security solutions, recently uncovered a malicious installer masquerading as the official Zoom client for macOS. The installer is distributed through unofficial channels and is deliberately crafted to look identical to Zoom’s legitimate download page. When a user runs the package, the malware performs a “double installation”:

1. Legitimate Zoom binary – The real Zoom client is installed in the expected location, allowing the user to join meetings without suspicion.
2. Hidden infostealer – A second payload is dropped alongside Zoom. This component silently monitors the system, captures credentials, browser cookies, and other sensitive data, then exfiltrates the information to a command‑and‑control (C2) server controlled by the attacker.

Jamf’s analysis notes that the installer “uses a sneaky way to bypass Apple’s Gatekeeper protection against malware.” By exploiting a weakness in the notarization process, the malicious package is allowed to run without triggering the usual warnings that macOS users rely on.

Technical Breakdown of the Gatekeeper Bypass

Gatekeeper is Apple’s first line of defense against unsigned or malicious software. It checks that an app is notarized by Apple and that its code signature matches the published hash. The fake Zoom installer sidesteps these checks through a combination of techniques:

1. Dual‑Package Wrapper

The malicious DMG contains two separate installer bundles:

• Zoom.pkg – A properly signed Zoom package downloaded directly from Zoom’s official servers. Because it is notarized, Gatekeeper passes it without issue.
• Stealer.pkg – An unsigned, malicious package that is embedded inside the same DMG but is not directly presented to Gatekeeper. Instead, the installer script extracts and runs it after the legitimate Zoom.pkg finishes.

2. Post‑Installation Script Abuse

During the Zoom installation, a post‑install script is executed with elevated privileges. The script performs the following steps:

• Verifies the integrity of the Zoom binary (a decoy check that always succeeds).
• Copies the hidden stealer payload to /Library/Application Support/Zoom/ where it blends in with legitimate Zoom files.
• Registers a launch daemon (com.zoom.helper.plist) that runs the stealer at login, ensuring persistence.

3. Code‑Signing Spoofing

The attacker re‑signs the stealer payload with a self‑generated certificate that mimics Zoom’s developer ID. macOS treats the certificate as valid for the duration of the installation, but the signature is never verified against Apple’s notarization service because the payload is never submitted for notarization.

These tactics collectively allow the malicious code to “fly under the radar” of Gatekeeper, a scenario reminiscent of the Zoom annotation flaw that was recently patched after an AI‑prompt exploit. For more context on how Zoom’s attack surface is being weaponized, see the detailed coverage here: https://ltdeveloperblogs.github.io/posts/zoomsday-hack-uncovered-using-fewer-than-20-ai-prompts.

Why It Matters for Users and Enterprises

Erosion of Trust in Trusted Platforms

Apple markets macOS as a secure ecosystem, and Gatekeeper is a cornerstone of that promise. When a widely used application like Zoom becomes a vector for stealthy malware, the perceived safety of the platform erodes. Users may become reluctant to install legitimate software, slowing productivity and increasing support overhead.

Data‑Theft Risks

The infostealer is capable of harvesting:

• Credentials – Saved passwords from browsers, keychains, and VPN clients.
• Corporate Information – Documents stored in local folders, meeting recordings, and shared drive links.
• Session Tokens – Tokens for cloud services (e.g., Microsoft 365, Google Workspace) that can be reused for lateral movement within an organization.

A successful breach can lead to credential stuffing attacks, ransomware deployment, or espionage. Enterprises that rely on Zoom for remote collaboration are especially vulnerable because the legitimate Zoom client provides a convenient foothold for the attacker.

Compliance Implications

Many regulated industries (healthcare, finance, government) must demonstrate that they protect personal data under standards such as HIPAA, GDPR, or PCI‑DSS. An undetected infostealer could constitute a violation, resulting in fines and reputational damage.

Industry Impact and Response

Vendor Reaction

Zoom has issued a statement confirming that its official installers are safe and urging users to download only from the official website. The company is also reviewing its distribution channels to detect and block repackaged installers.

Apple, for its part, is expected to release an emergency update to Gatekeeper that tightens verification of nested installers. Historically, Apple has responded quickly to similar threats—recall the rapid patch cycle after the “XcodeGhost” incident in 2015.

Security Community Mobilization

Jamf’s disclosure has sparked a wave of analysis across the security community. Researchers are scanning popular download mirrors, third‑party app stores, and even corporate intranets for the same DMG hash. The incident also underscores the importance of endpoint detection and response (EDR) solutions that can spot anomalous post‑install scripts.

Broader Market Trends

The attack highlights a growing trend: malware that piggybacks on trusted software. As users become more security‑aware, attackers increasingly rely on “double‑installation” tactics to blend in. This mirrors the tactics seen in the Chinese Auto Giant Moves to Apple Wallet Car Keys article, where attackers attempted to exploit Apple’s ecosystem in the automotive domain. For a broader view of how Apple’s ecosystem is being targeted, see: https://ltdeveloperblogs.github.io/posts/yet-another-major-chinese-car-brand-is-preparing-to-support-car-keys-in-apple-wallet.

Mitigation and Best Practices

Immediate Steps for End Users

1. Download Only From Official Sources – Always obtain Zoom from https://zoom.us/download or the Mac App Store.
2. Verify Checksums – When a DMG is provided, compare its SHA‑256 hash with the value published on Zoom’s website.
3. Enable Full Disk Encryption – FileVault adds a layer of protection if the infostealer attempts to read unencrypted data.

Enterprise‑Level Controls

• Application Whitelisting – Use macOS’s built‑in spctl tool or a third‑party MDM to allow only signed, notarized Zoom binaries.

• Enable Gatekeeper Strict Mode – Administrators can enforce the --strict flag via spctl --master-enable --global-policy to reject any app that isn’t notarized, even if it’s bundled inside a signed installer.

• Monitor Launch Daemons – Regularly audit /Library/LaunchDaemons/ and ~/Library/LaunchAgents/ for unexpected com.zoom.* plist files. The malicious installer registers a daemon named com.zoom.helper.plist; its presence outside of Zoom’s official documentation is a red flag.

• Leverage Endpoint Detection & Response (EDR) – Deploy EDR rules that trigger on the creation of files in ~/Library/Application Support/Zoom/ that are not part of the official Zoom bundle, or on the execution of unsigned binaries from that directory.

Read the full breakdown originally published at https://ltdeveloperblogs.github.io/posts/this-fake-mac-zoom-installer-has-a-sneaky-way-to-bypass-gatekeeper/