Hardware Wallets Are an Economic Security Failure

The latest Ledger supply-chain attack isn't the problem. The entire hardware wallet industry is.

Following the latest Ledger supply-chain attack, I keep seeing the same advice from Bitcoin influencers:

"Don't buy from resellers."

"Buy directly from the manufacturer."

"Switch to Trezor."

"Use multi-vendor multisig."

And I'm wondering how many more disasters it will take before people recognize that hardware wallets themselves are the problem.

Not Ledger. Not Trezor. Not Coldcard.

The entire category.

Because almost everyone is missing the most important part of the threat model:

The economics of targeted attacks.

And once you understand those economics, the entire hardware wallet security model starts looking very different.

1. The Ledger attack is just the beginning

In October 2026, Ledger began investigating substantial cryptocurrency losses associated with devices purchased through CryptoBilis, an authorized reseller in Southeast Asia. (Ledger update)

On-chain investigators estimated suspected losses exceeding $86 million. (Bitquery investigation)

Ledger subsequently confirmed that at least one affected device contained an unauthorized hardware implant. (Investigation and scope)

The investigation is still establishing the full scope of what happened.

Naturally, the conversation immediately turned to reseller security, tamper-evident packaging, and which manufacturer customers should trust instead.

But there's something fundamentally wrong with that conversation.

Why assume a reseller is as deep as a supply-chain attack can go?

A reseller is only one point in a much longer chain.

There's the component manufacturer.

The chip supplier.

The assembly factory.

The firmware developer.

The quality-control process.

The packaging facility.

The logistics company.

The distributor.

The retailer.

Every stage involves people, procedures, organizations, and opportunities for compromise.

And every one of those opportunities has a price.

The Ledger incident demonstrates what can happen when an attacker reaches one part of that chain.

But what happens when the potential reward becomes large enough to justify going further upstream?

What happens when compromising someone at the factory becomes more profitable than compromising a reseller?

Or when an attacker can influence a component before it reaches the manufacturer?

Or when manipulating a single manufacturing process could affect thousands of devices?

The supply chain doesn't magically become secure because an attacker has to move one or two steps deeper into it.

Those additional steps simply introduce additional costs.

And costs are precisely what financial incentives can overcome.

Which brings us to the much bigger problem.

2. Imagine $100 billion sitting behind a product category

Let's do a simple thought experiment.

Imagine that hardware wallets from a particular manufacturer eventually secure $100 billion worth of Bitcoin.

One hundred billion dollars.

An attacker who manages to steal just 0.1% of that value walks away with:

$100 million.

Now ask yourself a question.

How much would somebody rationally spend to gain access to that money?

$100,000?

$1 million?

$10 million?

Would it be worth recruiting an employee?

Compromising a supplier?

Developing a sophisticated hardware implant?

Spending years researching the manufacturing process?

Of course the answer depends on the probability of success. But that's exactly how attackers calculate these things.

Expected payoff = probability of success × potential reward − cost of attack.

And in the case of Bitcoin, the potential reward can be extraordinary.

We're not talking about stealing customer information that somebody might eventually buy.

We're not talking about industrial secrets that might provide a competitive advantage.

We're talking about private keys controlling bearer assets.

If you obtain the keys and can spend the funds, you're dealing directly with the money itself.

The incentive is immediate and enormously powerful.

Now consider what happens as Bitcoin adoption grows.

A manufacturer secures more Bitcoin.

Its customer base grows.

Its devices become more widely used.

And the potential reward from compromising that manufacturer's ecosystem grows with it.

The security budget of the manufacturer can grow too.

But the attacker doesn't have to defeat the manufacturer's entire security budget.

The attacker only has to find one sufficiently profitable weakness somewhere in the extended system.

A security procedure that is economically effective against a $100,000 attacker may not withstand the attention of a $10 million attacker.

A supply chain that was relatively uninteresting when its devices secured a few million dollars becomes an entirely different proposition when those same devices collectively protect billions.

This is the fundamental contradiction in the hardware wallet business model.

The more successful a hardware wallet manufacturer becomes, the more financially attractive its ecosystem becomes as a target.

Growth doesn't solve the economic problem.

It can amplify it.

3. Even Apple can't keep its supply chain sealed

Consider Apple.

One of the world's wealthiest technology companies.

A company famous for keeping unreleased products secret until its carefully orchestrated launch events.

Apple has enormous financial resources, sophisticated supplier agreements, dedicated security teams, and decades of experience managing some of the most complex manufacturing operations on Earth.

Yet information still escapes.

In June 2026, Reuters reported that a breach involving Apple's manufacturing partner Tata Electronics exposed confidential information about the upcoming iPhone 18 Pro, including detailed component and supplier information. (Reuters, June 29)

Think about that.

Apple spends extraordinary resources protecting its unreleased products and manufacturing secrets.

And still, information from inside its extended manufacturing ecosystem finds its way into unauthorized hands.

This was a data breach, not a hardware implant. But it illustrates something crucial about supply-chain security.

Even enormous organizations cannot completely control every person, system, and company involved in producing their devices.

Now think about the relative economic incentives.

What's the potential reward for obtaining an unreleased iPhone design?

Perhaps valuable industrial information, a competitive advantage, or media attention.

Now compare that with gaining access to Bitcoin private keys controlling $100 million.

The difference is staggering.

If an attacker is willing to compromise a supply chain for industrial secrets, what happens when the reward is direct access to bearer assets?

And if Apple, with its extraordinary resources, cannot eliminate unauthorized access throughout its extended supplier ecosystem, why should we assume a much smaller hardware wallet manufacturer can guarantee that nobody has tampered with its products?

Security is not simply a question of how much the manufacturer cares. It's a question of whether its defenses remain economically effective against the incentives facing its attackers.

And hardware wallets create exceptionally attractive incentives.

4. Trezor is not the escape hatch

This is where the usual advice becomes especially absurd.

Ledger has a problem?

Buy Trezor.

Trezor has a problem?

Buy Coldcard.

Coldcard has a problem?

Buy something else.

And every time, the solution conveniently involves buying another specialized Bitcoin device.

But imagine millions of Bitcoiners abandoning Ledger and migrating to Trezor.

What happens to the amount of Bitcoin potentially secured by Trezor devices?

It increases.

What happens to the potential reward from compromising the Trezor ecosystem?

It increases too.

Changing brands doesn't eliminate the underlying economic incentives.

It merely redirects them.

And let's look at what happened over the past few months.

In July 2026, Coldcard disclosed a critical failure in its seed-generation entropy mechanism, affecting firmware released over several years. Weakly generated seeds were exploited, resulting in substantial Bitcoin thefts. (Coinkite security status)

In August, Trezor disclosed a breach involving shipping provider ShipMonk, exposing customers' names, contact information, and shipping addresses. The incident was later found to affect roughly 81,000 customers in total. (Trezor disclosure)

In September, Trezor disclosed another incident, this time involving its email provider Brevo. Attackers exported 347,149 marketing email addresses and used compromised email infrastructure to distribute phishing messages. (Trezor disclosure)

BitBox was affected by a breach of the same email provider, exposing subscriber addresses and enabling fraudulent messages. (BitBox disclosure)

Then, in October, came the Ledger reseller incident and the confirmed unauthorized hardware implant.

Different companies.

Different attack vectors.

Different failures.

Some compromised customer information. Others affected wallet security directly. Some involved the devices themselves. Others involved external service providers.

And that's the point.

A hardware wallet isn't merely a piece of hardware. It's an entire commercial ecosystem.

It's manufacturing, firmware, distribution, logistics, customer databases, support systems, websites, marketing infrastructure, and the people running all of them.

Some of these services are needed to produce the devices; others come with the business that sells them.

And together they create an identifiable concentration of people likely to own Bitcoin.

When attackers obtain a Trezor customer database, they don't have to wonder whether those people might have Bitcoin.

The association is already made.

When attackers compromise a hardware wallet supply chain, they don't have to wonder whether the manufactured device might eventually be used for valuable cryptographic operations.

That is precisely what it is designed for.

Hardware wallets advertise their own economic importance to attackers.

And the more successful the category becomes, the more valuable that targeting information becomes.

5. Multi-vendor multisig, or multiple nightmares?

This brings me to perhaps the most frustrating advice of all.

"Just use multi-vendor multisig."

Seriously?

Let's understand what we're actually talking about.

A 2-of-3 multisig requires two independent signing keys to authorize a transaction.

That's a legitimate and extremely useful security property.

If one signer is compromised, the attacker still doesn't have enough keys to spend.

But where does that security property come from?

From Bitcoin.

Not from Ledger.

Not from Trezor.

Not from Coldcard.

Multisig is a Bitcoin authorization model, not a hardware wallet shopping strategy.

Using several vendors can reduce dependence on one manufacturer's specific failure modes. But it does not eliminate the supply-chain risks associated with specialized Bitcoin signing devices.

You still have several identifiable hardware wallet manufacturers.

Several manufacturing ecosystems.

Several firmware implementations.

Several distribution channels.

Several sets of operational assumptions.

And now you have to evaluate, maintain, update, and recover a more complicated system.

You're diversifying manufacturers while remaining entirely within the same economically attractive product category.

That's not the same thing as escaping the underlying targeting problem.

The important question isn't whether three different vendors have three different logos.

It's whether the actual failure domains are sufficiently independent and whether the added complexity improves the entire custody system.

And if you genuinely need a 2-of-3 multisig, there's a very simple question nobody seems interested in asking:

Why do the three signers need to be purpose-built hardware wallets at all?

Why not three independent generic computers?

Three separately maintained environments?

Three signers running Bitcoin Core?

Nothing in Bitcoin's multisig model requires hardware wallets.

The industry has turned what should be a discussion about threshold authorization and independent failure domains into yet another product recommendation.

And somehow we're supposed to believe that purchasing three different specialized black boxes is the pinnacle of security engineering.

One targeted manufacturing ecosystem is already a nightmare.

Three targeted manufacturing ecosystems are multiple nightmares.

You can preserve the cryptographic benefit of multisig without accepting the entire hardware wallet industry's manufacturing assumptions.

So why voluntarily bring those assumptions into your system?

6. The solution is boring. And that's exactly why it works.

Here's the solution.

Stop buying manufactured black boxes whose entire commercial identity tells attackers they are designed to secure Bitcoin private keys.

Use generic hardware.

An ordinary computer.

A used ThinkPad.

A generic desktop PC.

A machine originally built for an enormous, heterogeneous market of people doing entirely different things.

Some of those computers are used for accounting.

Some for writing documents.

Some for software development.

Some for watching movies.

Some for browsing the internet.

And an extremely small fraction might eventually become dedicated offline Bitcoin signers.

Now consider the difference from an attacker's perspective.

If you're compromising the supply chain of a hardware wallet manufacturer, you know exactly what kind of users you're targeting.

People who have purchased specialized devices to secure cryptocurrency.

But when you're looking at the supply chain of generic computers, you're dealing with millions of machines used for countless unrelated purposes.

There's no reliable relationship between a generic computer's make or model and the amount of Bitcoin it might secure.

The market is vastly larger, more heterogeneous, and less informative about the financial value behind any individual device.

That's a fundamentally different economic proposition.

Consider the attacker's expected return on every additional dollar spent developing an exploit.

Why spend enormous resources compromising a broad, generic computing supply chain when a much more concentrated population of Bitcoin holders voluntarily buys devices advertised specifically for that purpose?

Attackers can target generic computers too.

But targeting ordinary hardware as a class is not the same economic problem as targeting specialized devices purchased disproportionately by Bitcoin holders.

The economic attractiveness of a target is determined not only by what it protects, but also by how easily an attacker can identify and reach that value.

Hardware wallets make that identification easier.

Generic hardware makes it less obvious.

And once you choose generic hardware, the next step is to dedicate it exclusively to Bitcoin operations.

Install a clean operating system.

I prefer Debian Stable.

Remove unnecessary software, services, and functionality.

Disconnect the signer from the network permanently.

Create and secure the wallet using Bitcoin Core.

Use a separate online computer running Bitcoin Core to track the blockchain, prepare transactions, and broadcast completed transactions.

Transfer unsigned transactions to the offline signer as PSBTs.

Verify and sign offline.

Return the signed transaction to the online computer for broadcast.

Maintain independently recoverable encrypted backups, protect them with a genuinely strong passphrase, and regularly test recovery.

Generic hardware. Minimal Linux. Bitcoin Core.

No specialized manufacturer required.

No hardware wallet vendor-specific recovery ecosystem.

No dependence on proprietary signing firmware.

No need to purchase your security from a company whose products are explicitly marketed as containers for Bitcoin private keys.

And Bitcoin Core brings something else to the table.

A long history of public scrutiny.

An extraordinarily important role in Bitcoin's infrastructure.

Extensive real-world use.

An open-source codebase that has been studied, tested, attacked, corrected, and improved for many years.

For me, that's a much more compelling software foundation than continually adding specialized custody products and their unique assumptions.

Less novelty.

Fewer unnecessary dependencies.

More control.

More transparency.

And a very different economic attack surface.

7. The hardware wallet industrial complex

Of course, you won't hear much about this from the average hardware wallet influencer.

There's no affiliate commission when someone repurposes an old computer.

No referral code for installing Debian.

No new hardware product launch for recommending Bitcoin Core.

No manufacturer-sponsored conference appearance for explaining how to build a minimal offline signing environment.

The hardware wallet industry has developed an entire marketing ecosystem around its products.

Manufacturers.

Affiliates.

Influencers.

Sponsorships.

Conference partnerships.

Product reviews.

Discount codes.

Endless comparisons between devices that all supposedly solve the same problem.

And every new security incident creates another opportunity to recommend a different product.

Something goes wrong with Ledger?

Here's my Trezor affiliate link.

Something goes wrong with Trezor?

Here's a Coldcard discount code.

Worried about the entire situation?

Great. Buy three different devices and call it multi-vendor multisig.

The solution is always more hardware wallets.

That's a remarkable business model.

It's worth asking how much of the advice comes from independently evaluated threat models and how much is simply a repetition of industry conventions reinforced by commercial incentives.

You don't need to assume every influencer is consciously dishonest to recognize the problem.

Financial incentives influence what gets discussed.

Professional relationships influence which assumptions get challenged.

And social incentives influence which opinions are considered acceptable within a particular industry.

If your income, audience, conference invitations, and professional relationships are tied to the hardware wallet ecosystem, challenging the entire category is unlikely to be professionally convenient.

But ordinary Bitcoin holders don't owe the hardware wallet industry anything.

They don't owe manufacturers recurring purchases.

They don't owe influencers affiliate commissions.

They don't owe anybody the acceptance of a particular custody architecture just because it has become fashionable.

Bitcoin security should be an engineering discipline, not a consumer electronics subscription model.

The questions worth asking are simple.

What exactly am I protecting against?

What assumptions does this device introduce?

What would a sophisticated attacker be willing to spend to compromise it?

How concentrated is the reward?

What dependencies can I eliminate?

And can I build the same security properties without relying on a specialized manufacturer?

Those are first-principles questions.

Everything else risks becoming cargo-cult security theater.

8. Stop treating the symptom

The latest Ledger incident is not a reason to buy a Trezor.

The Coldcard entropy failure was not a reason to buy a Ledger.

The Trezor supply-chain and service-provider incidents are not a reason to buy whichever device happens to be fashionable next.

These events should force us to reconsider the underlying security model.

The problem isn't simply that one manufacturer failed.

Or that one reseller was compromised.

Or that one firmware implementation contained a catastrophic bug.

Or that one logistics provider exposed customer data.

The problem is the enormous economic incentive created by an industry that manufactures identifiable devices whose entire purpose is to secure valuable bearer assets.

And this problem becomes more important, not less, as the amount of Bitcoin secured by those devices grows.

We've spent years arguing about which hardware wallet is best.

Which secure element is best.

Which vendor has the best reputation.

Which device has the most impressive security certification.

Which combination of manufacturers produces the most reassuring multisig setup.

All while largely ignoring the simplest question:

Why are we voluntarily concentrating Bitcoin custody inside recognizable, specialized manufacturing ecosystems in the first place?

The entire premise deserves to be challenged.

Bitcoin doesn't require a hardware wallet manufacturer.

Bitcoin doesn't require branded signing devices.

Bitcoin doesn't require proprietary firmware.

Bitcoin doesn't require security to arrive in an expensive little box.

It requires valid cryptographic keys, correctly implemented signing software, appropriate isolation, recoverable backups, and operational procedures that match the actual threat model.

We already have the hardware.

We already have Linux.

We already have Bitcoin Core.

And when necessary, we already have multisig.

The tools to build independent, understandable, long-term Bitcoin custody systems already exist.

We don't need an endless parade of specialized products to package those tools for us.

And we certainly don't need to make the entire hardware wallet industry an increasingly valuable honeypot for sophisticated attackers.

So the next time somebody tells you that the solution to another hardware wallet disaster is multi-vendor multisig, remember:

Three different logos don't eliminate the economics of targeted attacks.

And buying more security products isn't the same thing as improving your security.

Stop treating every new incident as an isolated failure of the wrong brand.

Start looking at the economic incentives created by the entire category.

Ditch the targeted black boxes.

Use generic hardware. Run minimal Linux. Trust Bitcoin Core.

Build your security around Bitcoin, not around the hardware wallet industrial complex.

Practical context

Core wallet encryption protects private key material; it does not hide every transaction record, public key or label. Keep the passphrase separately recoverable, make a fresh backup after encryption or relevant wallet changes, and test restoration. An outer encrypted archive adds privacy and another recovery step. Bitcoin Core wallet documentation.