Exodus's .deb leaves two menu entries on Linux

Installing Exodus on Linux takes about two minutes; deciding which file to download is where most people stall. Exodus ships exactly two Linux artifacts, and picking the wrong one turns a short install into an afternoon of dependency errors.

Do You Need the .deb or the .zip for Exodus on Linux?

Use the .deb if you run a Debian-based distribution — Ubuntu, Linux Mint, Pop!_OS, or Zorin OS — and the .zip for everything else, including Fedora, Arch, openSUSE, and NixOS. Those are the only two Linux builds Exodus publishes . There is no official AppImage, Snap, Flatpak, RPM, AUR package, or apt repository, and Exodus's own installation documentation instructs users to download directly from exodus.com and never from third-party websites, distribution platforms, or package managers.

Quick Answer: Debian-based distros (Ubuntu, Mint, Pop!_OS, Zorin) install the Exodus .deb; all other distros use the portable .zip. Those are the only two official Linux builds. The current release is 26.8.26, dated 26 August 2026, and both artifacts require an x86_64 CPU.

The current desktop build is 26.8.26, published 26 August 2026 . Exodus uses date-based versioning in a YY.M.DD pattern, so the version number doubles as the release date — a useful check that you are not installing a stale mirror. Filenames follow the same convention on both formats: exodus-linux-x64-26.8.26.deb and exodus-linux-x64-26.8.26.zip, both available from exodus.com/download, with per-build SHA256 hashes published on the version-history page.

The .deb is the easier path on Debian derivatives, but it carries one documented quirk. Its packaging leaves a redundant .desktop file and a desktop-install script inside /usr/lib/exodus, which is why some users end up with two Exodus entries in their applications menu, each pointing at a different Exec line . Both usually launch the same wallet, so it is cosmetic rather than dangerous — but it is the most common "did my install go wrong?" moment on Ubuntu, and it is covered in detail later in this guide.

One constraint applies to both formats and cannot be worked around: Exodus Desktop requires an x86_64 CPU, a 64-bit Linux install on the latest or an LTS release of a major distribution, and 8 GB of RAM for optimal performance . ARM and RISC processors are explicitly unsupported, which rules out Raspberry Pi boards, ARM Chromebooks, and Apple Silicon running Linux. The x64 in the filename is the tell — there is no ARM equivalent waiting elsewhere on the download page.

.deb vs .zip: Full Comparison for Linux Users

Exodus ships exactly two Linux artifacts, and the choice between them is decided by your package manager, not your preference. The .deb is for Debian derivatives — Ubuntu, Linux Mint, Pop!_OS, Zorin — where a single apt command handles installation and menu registration. The portable .zip is for everything else: Fedora, openSUSE, Arch, NixOS, and any distribution without APT . There is no official AppImage, Snap, Flatpak, RPM, AUR package, or apt repository — the two files on exodus.com/download are the complete official set .

The .deb wins on convenience. APT resolves shared-library dependencies during install, writes the application entry, and gives you a clean uninstall path. Exodus also documents a graphical route: double-click the downloaded file, and if nothing happens, set your desktop environment's Software Install handler as the default application for .deb files, then launch Exodus from the app drawer . Its one documented cost is cosmetic: the package leaves a redundant .desktop file and a desktop-install script inside /usr/lib/exodus, which is why some users end up with two Exodus icons in the applications menu.

The .zip trades that convenience for control. You unzip the archive, place the resulting folder somewhere permanent — Exodus's own documentation uses /home/satoshi/Exodus-linux-x64 as the example — and launch through exodus.desktop or the Exodus binary . Running ./install-desktop-file.sh from inside that folder adds the menu entry and the exodus:// protocol handler. The practical catch: the script must be executed from a terminal with bash install-desktop-file.sh, because double-clicking it in a file manager typically appears to do nothing at all. On stripped-down systems it can also fail with failed to execvp: xdg-settings, which is resolved by installing xdg-utils.

One constraint applies equally to both formats and surprises users migrating from Windows or macOS: Exodus does not auto-update on Linux. On the other two platforms, new builds download in the background and apply on next launch; that mechanism is simply absent from the Linux client . Every release — the current one is 26.8.26, published 26 August 2026 under Exodus's YY.M.DD date-versioning scheme — has to be fetched again from the releases page and installed over the existing version. Exodus advises confirming that your 12-word recovery phrase is written down before you run any update .

That makes the decision straightforward. If you are on a Debian derivative and want the fewest commands, take the .deb and accept the possible duplicate menu entry. If you are on anything else — or you want no package-manager footprint, or you keep versions side by side — take the .zip. Exodus support has itself pointed users toward the .zip when the .deb misbehaves, so the archive doubles as the fallback path rather than a lesser option.

The .deb's Duplicate Menu Entry Quirk, Explained

The duplicate menu entry is a packaging artifact, not a malfunction: the Exodus .deb ships both a .desktop file and a desktop-install script inside /usr/lib/exodus, and each can register an applications-menu entry with a different Exec path . The visible symptom is two identically named "Exodus" icons in your app drawer after a single install. Both usually open the same wallet and the same encrypted data directory, so nothing is duplicated at the wallet level — only the launcher.

Because the two entries can point at different binary paths, they are not always interchangeable in practice. One may invoke the installed binary directly while the other routes through a wrapper, which is why some users report that one icon launches cleanly and the other appears to do nothing. If you hit that split behaviour, note which icon works before deleting anything.

The cleanest fix is to remove whichever launcher you do not want and refresh the menu cache:

• Find the launchers. Check both ~/.local/share/applications (per-user, written by the desktop-install script) and /usr/share/applications (system-wide, written by the package).
• Compare the Exec= lines. Open each exodus.desktop file and keep the one whose Exec path launches successfully.
• Remove the redundant file. Delete the user-level copy with rm, or the system-level copy with sudo rm. Never run the wallet itself as root — removing a file with sudo is fine, launching the app with it is not.
• Refresh the menu. Log out and back in, or run update-desktop-database ~/.local/share/applications, so the desktop environment stops caching the stale entry.

If the duplicate is only cosmetic and the wallet works, leaving it alone is a legitimate choice. The entry costs nothing operationally, and it will reappear on the next manual update anyway — Linux has no auto-update path, so every version bump means re-installing the newer package over the existing one . Deleting the stray .desktop file after each install becomes a small recurring chore rather than a one-time fix.

When the .deb causes deeper problems — failed launches, unmet dependencies that sudo apt --fix-broken install does not clear, or menu entries that keep pointing at broken paths — Exodus's own support position is to stop debugging the package and switch formats.

"Debian-based distributions should use the .deb for an easier install; non-Debian distributions should use the .zip." — Exodus installation guidance (source: Exodus Support), with support staff directing users to the .zip when the .deb misbehaves.

That fallback is straightforward: remove the package with sudo apt remove exodus, download exodus-linux-x64-26.8.26.zip from the official download page , and run ./install-desktop-file.sh from a terminal inside the unzipped folder to register exactly one menu entry plus the exodus:// protocol handler . Your wallet data is unaffected by the format swap — but confirm your 12-word recovery phrase is written down offline before you uninstall anything .

System Requirements: x86_64 CPU, 8GB RAM, and What Won't Work

Exodus Desktop for Linux runs only on 64-bit x86_64 hardware, requires 8 GB of RAM for optimal performance, and expects the latest or an LTS release of a major distribution . ARM and RISC CPUs are explicitly unsupported, so no official build exists for a Raspberry Pi, an ARM-based Chromebook, or an Apple Silicon Mac running Linux in a virtual machine . Check the architecture before you download anything else.

The filename is the giveaway. Every Linux artifact Exodus ships is named exodus-linux-x64-<version>.deb or exodus-linux-x64-<version>.zip — the current build being 26.8.26, released 26 August 2026 . There is no arm64 or aarch64 counterpart on the download page, and none is planned in the published artifact list . Confirm your own architecture in one command before proceeding:

uname -m
# x86_64  -> supported
# aarch64 / armv7l / riscv64 -> not supported

If uname -m returns anything other than x86_64, stop. Neither package format will help, and emulation layers such as QEMU or Box64 are not covered by Exodus support. The practical alternatives on ARM hardware are the Exodus mobile app or the browser extension, both of which use the same 12-word recovery phrase — the item that actually restores your wallet, as distinct from the app password, which only protects local application data .

RAM is a performance floor rather than a hard gate. Exodus is an Electron application, so the 8 GB figure reflects a Chromium renderer plus multi-chain portfolio syncing running alongside a desktop environment . On 4 GB machines the app may still launch, but expect slower sync and heavier swap use, particularly with several portfolios enabled.

Distribution choice matters less than package completeness. Server images, netinstall builds, container-based desktops and minimal window-manager setups routinely omit GUI libraries that Electron assumes are present. If the binary exits immediately or renders a blank window on such a system, install the usual GUI dependency set before troubleshooting anything else:

• libgtk-3-0 — the GTK toolkit Electron's window chrome draws through
• libnotify4 — desktop notification support
• libnss3 — Mozilla NSS, used by Chromium for TLS and certificate handling
• libxss1 — X11 screensaver extension, queried for idle detection
• libasound2 — ALSA audio, linked by Chromium even when muted

One caveat on the older guidance: Exodus's documentation also mentions libgconf-2-4 for some newer Linux releases , but GConf is deprecated and the package was dropped from Ubuntu 22.04+ and Debian 12+ repositories. If apt cannot find it, do not go hunting through third-party mirrors — launch the application first and treat the missing package as a non-issue unless a specific error names it.

Step-by-Step: Installing the .deb on Debian-Based Distros

Installing Exodus on a Debian-based distribution takes one command: download exodus-linux-x64-26.8.26.deb from exodus.com and run sudo apt install ./exodus-linux-x64-26.8.26.deb. Exodus Desktop 26.8.26 shipped on 26 August 2026 , and the .deb is one of exactly two Linux artifacts the company publishes . Debian derivatives — Ubuntu, Mint, Pop!_OS, Zorin — should take this path; everything else uses the .zip .

The terminal route is the one worth defaulting to, because it prints its errors instead of swallowing them. Download the package from exodus.com/download, then work from the directory the file landed in:

cd ~/Downloads
sha256sum exodus-linux-x64-26.8.26.deb
# expect: 8e98c194ae81e88b8a8584da01ca58c71f253f9550e9a7871d9a47ed845ba104
sudo apt install ./exodus-linux-x64-26.8.26.deb

The hash check is optional in the sense that apt will not enforce it, and mandatory in the sense that nothing else in this process authenticates the file. Exodus publishes a PGP-signed hashes file per build; for 26.8.26 the .deb SHA256 is 8e98c194ae81e88b8a8584da01ca58c71f253f9550e9a7871d9a47ed845ba104 . If the two strings do not match character for character, delete the download and start over. The leading ./ in the apt command is not decorative either — without it, apt treats exodus-linux-x64-26.8.26.deb as a repository package name and fails with "unable to locate package."

The graphical route works too, and Exodus documents it: double-click the .deb file in your file manager. If double-clicking appears to do nothing at all, the cause is almost always the file association rather than the package — set your system's Software Install handler as the default application for .deb files, then try again . On GNOME-based desktops that means right-clicking the file, opening Properties, and pointing "Open With" at Software Install. Once the graphical installer opens, the flow is a single Install button plus a password prompt.

One error message accounts for most failed installs on this path. If apt reports unmet dependencies — a stripped-down or minimal install missing a GUI library — run:

sudo apt --fix-broken install

That resolves the ordinary cases by pulling the missing packages from your distribution's own repositories. If it does not, the remaining suspects are the standard Electron GUI dependencies: libgtk-3-0, libnotify4, libnss3, libxss1 and libasound2.

After the install completes, launch Exodus from your desktop environment's app drawer rather than the terminal . Here is where the earlier packaging quirk shows up in practice: expect to find two Exodus entries in the applications menu, produced by the redundant .desktop file and desktop-install script left inside /usr/lib/exodus. Two icons is the normal outcome of a successful install, not evidence of a broken one — pick the entry that launches correctly and hide or ignore the other. Only if neither entry starts the application do you have a real failure to diagnose, and at that point Exodus support's own fallback is to abandon the .deb and use the portable .zip instead.

Two final steps before you put any funds in. Auto-update does not run on Linux , so note the version you installed — future updates mean re-downloading and re-installing over the top. And write down the 12-word recovery phrase offline immediately; the app password protects local application data only and cannot restore funds on its own .

Step-by-Step: Installing the .zip on Any Linux Distro

The portable .zip is the supported path for every non-Debian distribution — Fedora, openSUSE, Arch, NixOS — and the fallback Exodus support itself recommends when the .deb misbehaves . There is no installer and no package database entry: you unzip exodus-linux-x64-26.8.26.zip , put the folder somewhere permanent, and optionally run one script to register the menu entry. Four steps, roughly two minutes, and the only irreversible decision is where the folder lives.

1. Download and unzip to a stable location. Take the archive from exodus.com/download — never a mirror — and extract it where it will stay. Exodus's own documented example is /home/satoshi/Exodus-linux-x64 . That detail matters more than it looks: the desktop entry created in the next step hard-codes the absolute path to the executable, so moving or renaming the folder afterwards silently breaks the menu shortcut and the protocol handler. Pick the final home first — a directory under $HOME is the usual choice, since it needs no root and survives system upgrades.

unzip exodus-linux-x64-26.8.26.zip -d ~/Exodus-linux-x64
cd ~/Exodus-linux-x64

2. Register the menu entry from a terminal. Inside the unzipped folder, install-desktop-file.sh registers both the applications-menu entry and the exodus:// protocol handler used for deep links . Run it explicitly with bash:

bash install-desktop-file.sh

Double-clicking the script in a file manager usually appears to do nothing — most desktop environments either open it in a text editor or execute it without a visible terminal, so any error scrolls past invisibly. Running it from a shell is the difference between a working shortcut and a mystery. This step is optional in the strict sense: skipping it leaves you with a fully functional wallet that you launch by path rather than from the app drawer.

3. If the script fails with failed to execvp: xdg-settings. That error means xdg-utils is absent, which is common on minimal or server-derived installs where no full desktop metapackage was pulled in. Install it and rerun the script — the operation is idempotent, so a second run is safe:

• Fedora / RHEL family: sudo dnf install xdg-utils
• openSUSE: sudo zypper install xdg-utils
• Arch: sudo pacman -S xdg-utils
• Debian-family (if using the zip anyway): sudo apt install xdg-utils

4. If the menu entry still will not launch, run the binary directly. Exodus's documented fallback is to execute the Exodus file in the unzipped folder . Extraction sometimes drops the executable bit, so set it first:

chmod +x Exodus
./Exodus

Launching this way also gives you the console output, which is what you want if the window never appears — the sandbox and shared-library errors covered next both surface there. Note that the same manual-update reality applies to the .zip: because the archive is self-contained, updating means downloading the newer build and replacing the folder contents in place, keeping the same path so your shortcut survives . Run the published SHA256 check against the archive before you extract it — the expected value for the 26.8.26 zip is 3b5a8cadb73aa64e23e58f2819a3d5adab2e857780991ace2c70ea63b56e42ff .

Troubleshooting: Sandbox Permissions, Missing Libraries, Launch Failures

Most Exodus launch failures on Linux trace back to three causes: broken Electron sandbox permissions, a missing shared library on a stripped-down install, or a desktop entry that never registered. Exodus's own support documentation prescribes fixing chrome-sandbox ownership with sudo chown root chrome-sandbox followed by sudo chmod 4755 chrome-sandbox when the wallet refuses to start on first run . None of these failures affect wallet data — the 12-word recovery phrase is independent of the binary that reads it.

The table below maps the four failures that account for most first-run reports to their cause and the documented remedy.

The sandbox fix deserves a precise reading, because the two commands look similar to running the wallet as an administrator and are not the same thing. chown root and chmod 4755 apply to the chrome-sandbox binary that ships inside the Exodus folder, not to Exodus itself. Electron requires that helper to be root-owned with the setuid bit set so it can build the sandbox that isolates the renderer process; without it, Chromium refuses to start rather than running unsandboxed. Exodus is explicit that you should never run the wallet as root or through sudo, and never append command-line flags unless Support has specifically asked for them . Flags circulating in forum threads — most often --no-sandbox — trade the isolation layer for a launch, which is a poor bargain in software that holds private keys.

The libgconf-2-4 case is the one where following the documentation literally can waste an afternoon. Exodus's support article still lists both an apt example for Debian and Ubuntu and a yum example for Fedora and Red Hat derivatives , but GConf has been deprecated across the ecosystem and the package no longer exists in Ubuntu 22.04+ or Debian 12+ archives. If apt returns "unable to locate package," that is expected behaviour on a current release, not a broken sources list. Do not add third-party PPAs or pull a .deb from an unmaintained mirror to satisfy it — that reintroduces exactly the untrusted-source risk that makes Linux crypto wallet installs dangerous in the first place. Launch Exodus and see whether it starts; on modern builds it generally does.

When a launch failure resists all of the above, the fastest diagnostic is to start Exodus from a terminal rather than the applications menu. Running ./Exodus from the install directory prints the underlying error to standard output instead of silently discarding it, which turns "nothing happens" into a named missing library or a specific permission denial you can act on . If the .deb install is the source of the trouble, Exodus support has itself recommended falling back to the portable .zip build, which sidesteps package-manager state entirely . Before reinstalling anything, confirm your 12-word recovery phrase is recorded offline — the app password protects local application data only and cannot restore funds by itself .

Verifying Your Download, Updating Manually, and Avoiding Fake Exodus Wallets

Verification is a two-minute step that closes the largest remaining gap in a Linux Exodus install: proving the file you downloaded is the file Exodus published. Exodus ships a release-hashes text file with every desktop build, and the one for version 26.8.26 (released 26 August 2026) is a PGP-signed SHA512 message listing SHA256 hashes for each artifact . For Linux the published values are 8e98c194ae81e88b8a8584da01ca58c71f253f9550e9a7871d9a47ed845ba104 for the .deb and 3b5a8cadb73aa64e23e58f2819a3d5adab2e857780991ace2c70ea63b56e42ff for the .zip . Run sha256sum against your download and compare character by character; a mismatch means stop, delete the file, and re-download from exodus.com/download.

sha256sum exodus-linux-x64-26.8.26.deb
# expected: 8e98c194ae81e88b8a8584da01ca58c71f253f9550e9a7871d9a47ed845ba104

sha256sum exodus-linux-x64-26.8.26.zip
# expected: 3b5a8cadb73aa64e23e58f2819a3d5adab2e857780991ace2c70ea63b56e42ff

The same hashes file points signature verification at Exodus Movement's Keybase PGP key, fingerprint ef2ccd36c16a8b90da1932e0926dc59fbb75b328, for anyone who wants to confirm the manifest itself rather than just the binary . Verification is available but entirely manual — nothing in the install path checks it for you.

Why "official site only" is a hard rule, not boilerplate

Exodus's installation documentation states that you should download Exodus directly from exodus.com and never from third-party websites, distribution platforms, or package managers . That includes the Flathub listing io.exodus.Exodus, which Flathub itself marks Unverified, Proprietary and Medium Risk, and which states on the page that the wrapper is not verified by, affiliated with, or supported by Exodus . Its public manifest is transparent — it wraps the official Exodus zip on an Electron base app — but the pinned URL is for exodus-linux-x64-26.3.11.zip, roughly six months behind the current 26.8.26 build .

The cost of ignoring this is documented. In February 2024 a counterfeit "Exodus" app, published under the name "Movement Exod," appeared in Canonical's Snap Store with a convincing logo and screenshots; one user restored his wallet inside it and lost roughly 9 BTC — about $490,000 at the time . Analysis of the package found it was a Flutter application a fraction of the genuine client's size, while the real Exodus desktop build is Electron and ships with a full multi-hundred-megabyte runtime the fake never bundled . Snap Store moderators have since catalogued dozens of similarly disguised fake wallet snaps that get taken down and republished under new names, many using homoglyph substitution — near-identical Unicode look-alike characters swapped into the name — to slip past filters, as documented on the Snapcraft forum .

"The user has lost around 9 BTC — roughly $490,000 — by entering their recovery phrase into a fake wallet published in the Snap Store," wrote Alan Pope, former Snap Advocacy lead at Canonical, in his account of the incident (source: popey.com, 2024-02).

Updating on Linux is a manual, scheduled task

Auto-update is enabled by default on Windows and macOS but is not available on Linux . Updating means re-downloading the newer .deb or .zip from the official page and installing it over the existing version . Practically:

• Set a recurring calendar reminder — monthly is reasonable given Exodus's date-based YY.M.DD release cadence — to check exodus.com/releases for a build newer than the one you are running.
• Confirm your 12-word recovery phrase is written down offline before you update, which is Exodus's own stated precaution .
• Verify the new file's SHA256 against that release's hashes file before installing — every update is a fresh opportunity to install the wrong binary.
• Never type a recovery phrase into a wallet whose provenance you have not confirmed. The 12-word key restores funds; the app password only protects local application data .

The concrete takeaway: pick the format your distribution actually calls for — .deb on Debian derivatives, .zip everywhere else — download it only from exodus.com, check its SHA256 against the published hashes file before it touches your system, back up the 12-word key offline, and put a monthly reminder in your calendar to repeat the process. Those five steps cover the package-format decision, the duplicate-menu quirk, the sandbox and library failures, and the counterfeit-wallet risk in one routine. Everything else on Linux is a variation on them.

Frequently asked questions

Does Exodus have an official AppImage, Snap, or Flatpak for Linux?

No. Exodus publishes exactly two Linux artifacts — a .deb package and a portable .zip archive — and nothing else is official . There is no official AppImage, Snap, RPM, AUR package, or apt repository. A Flatpak does exist on Flathub under the ID io.exodus.Exodus, but the listing is labelled Unverified, Proprietary and Medium Risk, and the page states that the wrapper is not verified by, affiliated with, or supported by Exodus . Its build manifest simply repackages the official zip and is pinned to exodus-linux-x64-26.3.11.zip — roughly six months behind the current 26.8.26 build . Exodus's own installation guidance is to download only from exodus.com and never from third-party sites, distribution platforms, or package managers.

Why does installing Exodus's .deb create two icons in my applications menu?

Because the package registers a desktop entry through the normal Debian mechanism and also ships a redundant .desktop file plus a desktop-install script inside /usr/lib/exodus. Both end up visible to the applications menu, and because their Exec lines differ, the desktop environment treats them as two separate programs rather than deduplicating them. It is a packaging artifact, not a sign of a compromised or duplicated install — both entries launch the same binary. The fix is to delete the redundant .desktop file and refresh the menu database; the entry installed by the package itself is the one to keep. If the .deb continues to misbehave in other ways, Exodus support has recommended removing it and falling back to the portable .zip build instead .

What are the minimum system requirements for Exodus on Linux?

Exodus Desktop requires a 64-bit Linux system running the latest or an LTS release of a major distribution, an x86_64 CPU, and 8 GB of RAM for optimal performance . ARM and RISC processors are explicitly unsupported, which rules out Raspberry Pi boards, ARM-based Chromebooks, and Apple Silicon machines running Linux . The x64 in the filename exodus-linux-x64-26.8.26.deb is the practical tell — there is no ARM artifact to download. On stripped-down or minimal installs you may also need standard GUI libraries such as libgtk-3-0, libnotify4, libnss3, libxss1 and libasound2 before the Electron client will start.

Does Exodus auto-update on Linux like it does on Windows and macOS?

No. Auto-update is enabled by default on Windows and macOS, where new builds download in the background and apply on the next launch, but auto-update is not available on Linux at all . Linux users must update manually: re-download the newer .deb or .zip from the Exodus releases page and install it over the existing version. Because Exodus uses date-based versioning (YY.M.DD), the current build number doubles as its release date — 26.8.26 shipped on 26 August 2026 . Exodus advises confirming that your 12-word recovery phrase is written down before you update, since that phrase — not the app password — is what restores the wallet .

How do I verify my Exodus Linux download is authentic?

Run sha256sum on the downloaded file and compare the output against Exodus's published release-hashes file for that build before installing. For version 26.8.26, the Linux .zip hash is 3b5a8cadb73aa64e23e58f2819a3d5adab2e857780991ace2c70ea63b56e42ff and the .deb hash is 8e98c194ae81e88b8a8584da01ca58c71f253f9550e9a7871d9a47ed845ba104 . The hashes file is itself a PGP-signed SHA512 message, and signature verification points to Exodus Movement's Keybase key with fingerprint ef2ccd36c16a8b90da1932e0926dc59fbb75b328. Verification is manual — there is no built-in checker — but it is the step that separates a genuine build from a counterfeit. The stakes are documented: in February 2024 a fake "Exodus" app in Canonical's Snap Store cost one user roughly 9 BTC, about $490,000 at the time . Analysis found the imposter was a Flutter app a fraction of the genuine client's size, while the real Exodus desktop build is Electron . Snap Store moderators have separately catalogued dozens of similarly disguised fake wallet snaps that reappear under new names using homoglyph character substitution to evade takedown . Store confinement badges offer no protection here, because sandboxing does not prevent an app from exfiltrating a recovery phrase the user types into it.

Enjoyed this article? Subscribe to get new stories by email whenever they're published.

Subscribe