Ledger Live MacBook Pro: Who Relies on the Desktop App and How Keys Stay Offline
Safe Ledger Live Use on Your MacBook Pro starts with one rule: install the companion application only from the vendor’s own address and verify its signature before the first launch. Everything else – pairing, address review, backup storage – rests on that single step. Get it wrong and no later check recovers the funds.
How the Companion App Interacts With a Hardware Signer
The desktop client is a screen and a relay, not a vault. It builds transactions, displays balances fetched from public block explorers, and hands unsigned payloads to the signer over a cable or a paired wireless link. The device holds the seed, renders the destination address on its own display, and returns a signature only after a physical button press.
Where the seed material actually rests
The recovery phrase and every key derived from it stay inside the signer’s secure element, a tamper-resistant chip that will not export them under any command. During setup that chip generates the words from its own randomness and shows them once on its screen for a paper or metal backup. The laptop receives only public keys – enough to compute addresses and read balances, never enough to spend. A stolen machine therefore yields no coins, and a lost device yields none either once the backup is restored elsewhere. Losing device and backup together is irreversible.
What the host software can and cannot do
The laptop-side client asks for signatures; it cannot manufacture them, and it cannot read the phrase. It can, however, be deceived or replaced: clipboard malware and counterfeit builds alter what the window shows. The signer’s own display is the reference point, because the payload it renders is assembled inside the chip. The client also cannot push a firmware update without a confirmation on the device, and it cannot move value while the signer is unplugged or out of range.
What a wireless pairing adds to the setup
Bluetooth support removes the cable but creates a stored pairing between one computer and one signer, and that pairing record behaves like a credential. It is exchanged once and reused, typically held in the system keychain, so any process able to read that keychain can reach the device without a fresh code. Cable connections leave no such record behind. Delete existing pairings on machines you sell, lend, or stop trusting.
Which Holders Rely on It, and When the Setup Applies
It fits holders who keep assets for months or years and want spending authority separated from the machine that browses the web. It applies once a position is large enough to justify a dedicated device and the owner can keep a backup away from the laptop. Frequent intraday trading fits it poorly, because every spend needs a physical confirmation.
Long-horizon holders with one signing device
Buying, staking and occasional transfers are the natural workload: few transactions, each worth checking on a screen. The desktop client shows full addresses and fee options in one window, which makes a slow review practical rather than tedious. The trade-off is that one device is one point of failure; a destroyed signer without a readable backup means permanent loss. Keep the backup on metal or paper in a second location, not in a photograph or a cloud note.
Operators who split signing duties across people
Multi-signature arrangements place a separate device with each participant, and the desktop client becomes the coordination point where partial signatures are combined. A policy requiring more approvals than any single person holds means nobody can move funds alone. The weak link is the shared computer: if all participants enter their PINs under the same operating-system profile, the separation collapses. Give each signer its own account, or better, its own laptop.
People who manage holdings on someone else’s behalf
Executors, family members and advisors run the same software but face a different problem: they must be able to act without the original owner. Recovery depends entirely on the phrase, so the instructions, the backup and the device all have to reach the right person at the right moment. If any one of the three is missing, the assets are gone and no support desk can reverse it. Write the handover procedure down and rehearse it once while the owner is still present.
Desktop Client Versus Mobile, Browser and Software Wallets
The desktop client suits large, infrequent transfers that deserve a full-size screen for address checking. A phone app wins for quick confirmations and travel. Browser extensions that hand signing off to a device work well for on-chain applications, and software-only wallets stay the fastest and least protected option.
The table compares five routes on the criteria that decide real setups: where signing keys rest, how the interface reaches the signer, and the constraint that shows up in daily handling. Supported versions, pairing limits and fee schedules are published on the vendor’s official pages and change between releases.
| Route | Where signing keys rest | How the interface reaches the signer | Main constraint |
|---|---|---|---|
| Desktop companion on the laptop | Inside the hardware chip, never on disk | Wired cable or a stored wireless pairing | One machine profile at a time; version rules published officially |
| Mobile companion on a phone | Inside the same hardware chip | Wireless pairing or a short adapter cable | Smaller display for address comparison |
| Browser extension relaying to a device | Keys stay on the device; extension only moves data | Web page passes payloads to the signer | Each extension carries its own permissions and update history |
| Software wallet with keys on the drive | On the disk, guarded by a password | No device involved | Malware can copy the key file silently |
| Air-gapped QR or card signing | Inside an offline signer | Camera or removable storage | Slower; every hop needs manual checking |
A desktop setup fits the holder who moves funds a few times a month and wants the widest review surface; it does not fit someone who must sign from a train or a conference floor. Mobile apps cover that case but shrink the address-checking area, which raises the chance of a missed character. Browser extensions add convenience for on-chain activity while keeping keys on the device, though each one brings its own permissions. Software-only wallets suit small, active balances and serve poorly for savings. Exceptions exist: a signer paired to a phone can carry both roles.
Wireless pairing versus a cable
Cable connections carry no persistent credential, which is why they remain the default for large transfers. Bluetooth pairing is convenient, but the pairing secret stays on the computer and can be reused by anything that reads it. A cable also delivers power and reduces the chance of an interrupted session in the middle of a multi-signature flow. Choose wireless for small, frequent confirmations and a cable for anything you would rather not repeat.
Where a software wallet stops being adequate
A wallet whose keys sit on the drive is only as strong as the machine’s password and the absence of malware. Key files and phrases on disk can be copied without a trace; nothing in the design prevents it, because the application must read the key to sign. Signers solve that by keeping the key in a chip that refuses export, so theft of a file is not theft of the coins. Keep a software wallet for spending money and a signer for stored value.
What Goes Wrong Most Often, and Why?
The recurring failures are host-side: a counterfeit installer, a phrase typed into a website or a chat window, and a destination address swapped after a copy-and-paste. The chip rarely breaks; the workflow around it does. Each of these mistakes is preventable with a check that costs seconds.
Counterfeit installers and lookalike domains
A fake build is the most direct route to theft because it requests exactly what a genuine client never asks for: the recovery phrase. Search results, sponsored links and one-character typos in the web address are the usual delivery routes, and some counterfeit packages carry a valid developer certificate that the system accepts after a single override click. The defense is procedural: type the address yourself, compare the published hash, and treat any phrase prompt from a desktop window as evidence of compromise.
Destination addresses altered between screens
Malware that watches the clipboard can replace a pasted address before the transaction is built. Both ends of an address are derived from the same key material, so a swapped value looks plausible at a glance; comparing the first and last few characters on the signer’s display against the recipient’s own message catches it. Some malware waits for a second paste, which is why the check belongs at the final confirmation rather than at the copy.
Recovery words entered outside the device
No legitimate process needs the phrase typed into a computer, a browser, a support chat or a form. Restoring a signer means entering the words on the device itself, using its buttons. Any page, pop-up or message that requests them is an attempt to take the assets, and once submitted they can be moved without further access to the laptop or the device. That outcome cannot be reversed, and replacing the phrase afterwards means creating an entirely new account and migrating the balance.
How Do You Verify a Fresh Install Before Moving Funds?
Set aside roughly ten minutes and have the signer, its PIN, the checksum list published next to the download, and a small test amount ready. The procedure confirms that the file, the signature, the pairing and the address path are all genuine before a meaningful balance is exposed to them.
Step 1: Open the vendor’s own download page by typing its address rather than following a search result or an emailed link
Open the vendor’s own download page by typing its address rather than following a search result or an emailed link. Sponsored placements and typo domains sit above the real result, and a counterfeit build stays visually identical until it asks for recovery words.
Step 2: Compare the downloaded file’s hash against the value printed on that same page
Compare the downloaded file’s hash against the value printed on that same page. Hashes are published per release, so a mismatch means the file was altered or truncated; delete it and download again from the typed address.
Step 3: Check the application’s code signature and notarization status with the built-in system tools before the first launch
Check the application’s code signature and notarization status with the built-in system tools before the first launch. The operating system refuses unnotarized builds by default, so an override prompt is itself a signal to stop and re-examine where the file came from.
Step 4: Pair the signer and confirm that its screen shows the same receiving address as the application window
Pair the signer and confirm that its screen shows the same receiving address as the application window. The address on the device is generated inside the secure chip, so an exact match rules out host-side tampering for that specific address.
Step 5: Send a small test amount to that address and confirm receipt in the client and in a public block explorer before moving the rest
Send a small test amount to that address and confirm receipt in the client and in a public block explorer before moving the rest. A completed round trip proves the address, the network and the account path all line up while the exposure stays small.
What Still Changes Between Releases?
Firmware versions, supported operating-system releases, wireless behavior and the roster of integrated swap and staking partners all shift between publications. None of those details can be treated as fixed by anything written outside the vendor’s release notes. Compare the version you actually run against the current published list.
Firmware and application version pairing
An application build and device firmware are developed against each other, so a feature added to one may stay unavailable until the other catches up. Version numbers, minimum supported releases and deprecation notices appear in the vendor’s own notes – the official download and release page is the only source worth citing. Skipping several firmware generations is usually permitted but can disable a previously working feature, so check before a planned transfer rather than during one.
Third-party services embedded in the interface
Swap, buy and staking options inside the client are operated by outside firms, each with its own terms, fees and data handling. The signer still controls the signature, so those partners cannot move assets without a device confirmation, but they do see the destination and the amount. Availability varies by region and by account type, and the partner list changes without notice. Confirm the current providers and their conditions on the official page before relying on one.
Contested claims about wireless interception
Attacks described in public research target the wireless link – relaying or intercepting traffic while an attacker is physically close – and no public demonstration has extracted keys from the chip itself. That distinction matters: a relayed session still requires the owner to approve on the device unless the payload shown is misleading. Treat those findings as a reason to prefer a cable for large transfers and to read the device screen line by line, not as evidence that funds can move without approval.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Download Ledger Live Only from Ledger's Official Website on macOS: Verifying the Installer and Spotting Mirrors",
"description": "Download Ledger Live Only from Ledger's Official Website on macOS, because the maker's own page is the only retrieval path that pairs a signed, notarized installer with a digest printed by the same organisation. This article covers the verification routine, the lookalike sources, and the details that shift between releases."
}
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How Do You Verify a Wallet Installer Before Opening It on macOS?",
"step": [
{
"@type": "HowToStep",
"text": "Type the publisher's domain into the address bar instead of following a link from a message, an advertisement or a search result."
},
{
"@type": "HowToStep",
"text": "Download the installer from that page and leave it in the Downloads folder untouched."
},
{
"@type": "HowToStep",
"text": "Compute the file's SHA-256 digest with the shasum command in Terminal."
},
{
"@type": "HowToStep",
"text": "Inspect the code signature and notarization ticket with the codesign and spctl tools that ship with macOS."
},
{
"@type": "HowToStep",
"text": "Delete the file and restart the process if the digest, the signing entity or the notarization verdict disagrees with the page."
}
]
}
Download Ledger Live Only from Ledger’s Official Website on macOS – that single rule removes the most common failure mode for anyone holding keys on an Apple notebook. The installer served from the maker’s own domain carries a signature tied to the company’s developer identity and a digest printed on the same page, so a byte-level change becomes visible before the application is opened. Every other route, whether a mirror, a bundled updater or a sponsored search result, breaks that chain and leaves nothing authoritative to compare against.
Download Ledger Live Only from Ledger’s Official Website on macOS
One address serves the desktop build: the maker’s own site, which hosts a signed Apple disk image or installer package for current macOS versions. The company controls the build pipeline, submits the finished bundle for Apple’s notarization scan, and prints the matching file digest on the same download page. No mirror reproduces that combination.
How the Signing and Notarization Chain Is Assembled
A release is compiled by the vendor’s build system, signed with the Developer ID certificate Apple issues to that legal entity, then sent to Apple’s notary service, which returns a ticket stapled to the installer. Gatekeeper inspects that ticket the first time the bundle launches, and macOS holds the quarantine flag until the check completes. Because altering a single byte breaks the signature, a patched copy cannot present the same identity. Apple’s developer pages document current notarization rules, and the download page lists which macOS releases the build supports.
What the Download Page States Alongside the File
Each release page names the version string, the supported macOS range, a short changelog and, on most occasions, a checksum value for the installer. Those four items are worth copying before the download finishes, because they form the reference set compared against later. A reader who wants the authoritative numbers rather than a cached copy opens the maker’s download page directly. Version strings and supported-system lists move with each build, so figures seen last quarter may no longer apply.
Do You Actually Need a Desktop Wallet on a Mac?
Only if signing happens often or across several accounts. A large window makes address comparison and transaction review easier, and hardware keys connected by cable or Bluetooth pair with the desktop build. For occasional transfers, a phone app paired to the same device covers the same ground with fewer moving parts, and nothing about the desktop client improves key storage.
Tasks That Suit a Full-Screen Interface
Reviewing a long address string, comparing a destination against a saved contact, and checking contract data all benefit from a wider display and a physical keyboard. The desktop client also keeps a local record of account history that is easier to search than a phone screen allows. People running several accounts across different networks usually find the layout less error-prone during routine transfers, though the private keys continue to sit inside the hardware device rather than on the machine.
Cases Where a Phone or Browser Companion Fits Better
A paired mobile application handles everyday transfers and portfolio checks, and Bluetooth pairing removes the cable. Browser extensions, where the vendor publishes one, are convenient for web3 interactions but widen the attack surface because they run inside a browser session alongside other tabs. Anyone who signs rarely, travels without a laptop, or keeps a single account has little reason to install the desktop build; the marginal convenience does not justify a second place where something can go wrong.
Official Installer Versus Mirrors and Repackaged Builds
The vendor’s own download page is the only source that pairs a signed, notarized installer with a digest published by the same organisation. Mirrors, package-manager manifests and re-uploaded copies may deliver byte-identical files, but none of them lets a reader trace the file back to the publisher without trusting a third party. That difference decides the path.
The comparison below weighs five retrieval routes against four criteria: what actually arrives, how its authenticity can be checked, the practical constraint each carries, and where the chain of custody breaks. The final column settles most cases, because a route with no verifiable origin leaves nothing to compare against.
| Retrieval path | What arrives | How authenticity is checked | Main constraint |
|---|---|---|---|
| Publisher’s download page | Signed disk image with a stapled notarization ticket | Digest printed on that same page | Manual hash and signature check still required |
| Package manager cask | Automated install into the Applications folder | Manifest points at the publisher’s own address | Manifest can lag behind the newest release |
| File-sharing mirror or re-upload | Byte copy that may be patched or wrapped | Nothing authoritative, only a file name | No chain of custody back to the maker |
| Sponsored search placement | Landing page imitating the maker’s layout | None, the address differs from the real domain | Campaigns can run before they are reported |
| Message or forum attachment | Installer forwarded by another person | Unknown provenance, no published digest | Often unsigned or signed by an unrelated developer |
The publisher’s page fits a first installation, an upgrade and any situation where funds are at stake, and it is the only route supporting a hash check against an authoritative value. A package manager suits readers who already track manifest updates and accept a short delay behind the newest build. Mirrors, sponsored links and forwarded attachments fit no scenario of that kind; the one exception is a copy confirmed against a digest obtained from the publisher through a separate channel, which in practice means downloading twice.
Why a Published Digest Outweighs a Familiar File Name
File names are chosen by whoever uploads the file, so a tidy label such as Wallet-Installer.dmg says nothing about origin. A digest, by contrast, is a fixed-length fingerprint of the exact bytes, and any alteration produces a completely different string. The value only carries weight when it comes from a channel the reader already trusts, which is why the number printed beside the download button on the maker’s own page beats a checksum pasted into a forum reply or a video description.
Manifest Lag and the Package Manager Trade-Off
Package managers save keystrokes and keep versions tidy, but each manifest is maintained by volunteers or by the vendor’s staff, and the entry refreshes on its own timetable. A release published on a Friday may sit outside the manifest for a day or more, which is harmless for routine maintenance and awkward when a fix is urgent. Readers who accept that delay get reproducible installs; readers who need the newest build should fetch it from the source page.
Where Do Fake Wallet Installers Come From?
Most fraudulent installers arrive through paid search placements, misspelled domains, and direct messages that promise a fix, a bonus or an early update. The file is a disk image wrapped around a script that asks for the recovery phrase, or a patched copy that swaps destination addresses after installation. A browser padlock proves nothing about the builder.
Paid Placements and Typo Domains
Advertising networks sell the top slot to whoever bids, and a campaign pointing at a copy of the vendor’s page can run for days before anyone reports it. Domains are cheap and are often registered shortly before a campaign, with a character substituted or a hyphen inserted. Checking the address bar, rather than the page design, is the only reliable test, because a copied layout costs nothing to reproduce.
Update Prompts, Bundled Wrappers and Remote Offers
Fake updaters appear as browser pop-ups claiming a critical patch, and they tend to surface while a real release is in the news. Some installers carry extra payloads that stay dormant until a transaction is prepared, then substitute the destination address on screen or in the clipboard. An unsolicited call offering remote installation belongs to the same category of fraud, whatever the caller claims to represent.
How Do You Verify a Wallet Installer Before Opening It on macOS?
Verification means matching the file in the Downloads folder against values the publisher printed, then confirming Apple’s signature check passes. Have ready: the exact address of the vendor’s download page, a terminal window, and the digest or version string shown next to the download button. The whole check takes a couple of minutes and leaves a clear yes-or-no result.
Step 1: Reach the page by typing, not by clicking
Type the publisher’s domain into the address bar instead of following a link from a message, an advertisement or a search result. A typed address removes the redirect chain that sponsored placements and shortened links rely on.
Step 2: Save the file without opening it
Download the installer from that page and leave it in the Downloads folder untouched. Opening it before a hash check gives a malicious bundle the chance to run its first stage.
Step 3: Fingerprint the bytes
Compute the file’s SHA-256 digest with the shasum command in Terminal. The resulting string is matched character by character against the value printed on the download page, and a single wrong character means the file changed in transit or on the server.
Step 4: Read the signature and the notarization verdict
Inspect the code signature and notarization ticket with the codesign and spctl tools that ship with macOS. A valid result names the developer entity Apple vouched for, which should correspond to the company that published the page.
Step 5: Discard and restart on any mismatch
Delete the file and restart the process if the digest, the signing entity or the notarization verdict disagrees with the page. A mismatch is not a warning sign to investigate later; the copy is thrown away and the address is retyped from scratch.
What Changes Between Releases and What Readers Still Get Wrong
Version numbers, supported macOS ranges, digest values and release notes shift with every build, so any figure quoted in an article ages within weeks. Notarization requirements move when Apple changes its rules, and package-manager manifests lag behind the vendor’s page by hours or days. Treat the publisher’s download page and Apple’s developer documentation as the live references.
Release Cadence and Silent Policy Shifts
Desktop builds ship on an irregular schedule, sometimes several within a month when a security fix lands. Each one carries a new digest, and older digests stop appearing on the download page, which is why a checksum copied from a forum thread from last year is useless. Apple occasionally tightens notarization or Gatekeeper behaviour between major system versions, so a bundle that launched cleanly on one macOS release can produce a different prompt after an update.
Assumptions That Keep Circulating
Three beliefs survive every rewrite: that a padlock in the browser vouches for the file, that a mirror is acceptable when the checksum matches something posted there, and that an installed application can be trusted indefinitely. The first two confuse transport security with publisher identity, since a genuine page and a copy can both serve identical bytes over an encrypted connection. The third ignores how software ages once it stops receiving updates.
Q&A:
Can I use Ledger Live on a MacBook Pro that I also use for email and web browsing?
Yes, but treat the Mac as a display and network tool, not as a vault. Your private keys stay on the Ledger device and are not exposed to macOS. A compromised Mac can still change a wallet address on screen, swap clipboard data, or trick you into signing a bad transaction. For daily use, keep macOS updated, install software only from trusted sources, avoid cracked apps and unknown browser extensions, and use a separate macOS user account for crypto if you can. Always compare the receiving address and amount on the Ledger device before you approve. If you handle large amounts, consider a dedicated Mac or at least a clean account that you do not use for random downloads.
How can I check that the Ledger Live installer for macOS is genuine?
Go to Ledger’s official website by typing the address yourself or using a bookmark you saved earlier. Do not click search ads or links from emails, chat messages, or YouTube descriptions. On the download page, use the macOS file Ledger provides. After downloading, open the DMG and drag Ledger Live to Applications. You can check the app’s code signature in Finder: right-click Ledger Live, choose Get Info, and look for a valid Developer ID from Ledger. If macOS warns that the app cannot be checked or comes from an unknown developer, stop. Delete the file and download again from the official site. Ledger Live will never ask for your 24-word recovery phrase during installation or updates.
Where should I keep my recovery phrase if I use Ledger Live on a MacBook Pro?
Keep it off the Mac completely. Do not type it into Ledger Live, Notes, Photos, a browser, a password manager, or any app on macOS. Do not photograph it or store it in iCloud, Dropbox, Google Drive, or email. The phrase restores your funds, so anyone who sees it can spend them without your Ledger device. Write it on paper or stamp it into metal, then store it in a safe place that is not obvious. A second copy in a different secure location can help with fire or flood, but splitting it across cloud services adds risk. Ledger Live never needs your recovery phrase. If any app or website asks for it, that is a scam. If you use a passphrase, store it separately from the 24-word phrase and understand that losing it can lock you out.
Does Ledger Live on macOS need Bluetooth, and can I turn it off?
Ledger Live needs an internet connection to read balances and send transactions. Bluetooth is only needed if you use a Ledger Nano X, Ledger Stax, or another model that connects wirelessly. If you use a USB cable with a Nano S, Nano S Plus, or Nano X, you can turn Bluetooth off in macOS and in the Ledger device settings. For higher assurance, use USB and keep Bluetooth disabled when you are not using it. You can also deny camera, microphone, and location access to Ledger Live in System Settings > Privacy & Security. Ledger Live does not need those permissions to work.
My MacBook Pro is managed by my employer. Is it safe to install Ledger Live on it?
A work-managed Mac is usually a poor choice for crypto. Your employer’s IT team may have remote access, software inventory, configuration profiles, or screen monitoring tools. They may not be able to steal keys from the Ledger device, but they could see when you open Ledger Live, alter files, or capture your screen while you check addresses. If the Mac has MDM, assume the admin has broad control. Use a personal Mac instead. If you have no other option, create a separate user account, but know that MDM can still apply system-wide. Never enter your recovery phrase on that machine. Verify every transaction on the Ledger screen, and consider moving large holdings to a setup where the computer is fully yours.
I installed Ledger Live on my MacBook Pro from a search ad. How do I check whether it is the real app?
Close it and remove it. Open Safari and type ledger.com yourself. Download Ledger Live only from that page. After downloading, open the .dmg and drag the app to Applications. In Finder, right-click Ledger Live, choose Get Info, and look at the code signature. It should be signed by Ledger SAS. If macOS Gatekeeper blocks it, do not right-click Open just to bypass the warning unless you are sure the file came from ledger.com. Compare the SHA-256 hash if Ledger publishes one. If you already entered your recovery phrase into the app, move your funds to a new wallet generated by your Ledger device, because that phrase is no longer private. Ledger Live never asks for your 24-word phrase.
Is it enough to use Ledger Live on a MacBook Pro, or do I still have to watch for malware and phishing?
Ledger Live reduces risk because transaction signing happens on the Ledger device, but your Mac can still be a hostile place. Malware can change a crypto address in your clipboard, fake a Ledger Live window, log keystrokes, or take screenshots. So treat the Mac screen as a display, not as the final authority. The final authority is the Ledger screen. Before you approve, read the amount and recipient address on the device. If they do not match what you typed, cancel. Do not store your recovery phrase in Notes, Photos, iCloud, Google Drive, or a password manager. Do not type it into any app or website. Keep macOS updated, turn on FileVault, use a strong login password, and lock the screen when you leave. Remove remote-access tools and unknown browser extensions. Download apps only from trusted sources. For desktop use, connect the Ledger with the cable that came with it. Ledger Live desktop uses USB, not Bluetooth. If you use a Nano X, Bluetooth is for the mobile app.
What if I think my MacBook Pro was hacked while Ledger Live was open? Should I wipe the Mac or move my crypto first?
Do not type your recovery phrase into the Mac. Disconnect the Ledger. If you have another clean computer or phone, you can use that to check balances and prepare a transfer, but still approve only on the Ledger device. If the device PIN was not shared and the device is with you, your private keys should still be on the Ledger. The risk is that malware could trick you into signing a bad transaction or steal your Ledger Live password. Ledger Live password does not expose your recovery phrase, but it can let someone open your portfolio on that Mac. If you believe the recovery phrase was seen or typed anywhere, generate a new wallet with a new recovery phrase on the Ledger, then send all assets to the new accounts. Do not reuse the old phrase. After that, erase the Mac and reinstall macOS from Recovery Mode. Download Ledger Live again from ledger.com. Change passwords for email, exchanges, and any accounts you used on that Mac. Check exchange withdrawal addresses and API keys. If you are not sure, ask Ledger support through ledger.com, and never send your 24-word phrase to anyone, including support.
