mt logoMyToken
ETH Gas
EN

Ledger Confirms Tampered Wallets in Berlin as Two Dubai Units Join the Probe

Blockchain main2

Ledger has confirmed that tampered hardware wallets from the supply-chain incident it disclosed in October reached beyond Southeast Asia, and it has now named two additional locations. In an update to its incident investigation dated 19 November 2026, the hardware wallet maker said the devices found in Germany were “localized to Berlin,” and that it is investigating reports of two tampered units in Dubai.

The same page states that the pattern is unchanged: “Every device we have confirmed shows the same kind of physical modification, built to capture the recovery phrase during setup.” Ledger’s summary sentence is explicit about scope. “Our findings since then show tampered devices outside Southeast Asia. It is the same incident.”

For anyone who bought a Ledger signer in Berlin, the company’s guidance reaches back further than the announcement date. Ledger asks buyers who purchased in Berlin from January 2026 onward to contact its support team, which extends the practical exposure window to roughly 322 days, or about ten and a half months, before the 19 November update.

What the 19 November Update Actually Says

Read closely, the update separates three locations by evidentiary status rather than treating them as one finding, and the distinction matters for anyone deciding whether their device is in scope.

Southeast Asia remains an open file. Ledger says the investigation continues for the resellers it previously paused, and that it has found one confirmed case there involving a Ledger Nano Gen 5. Germany has moved from unverified reports to a located cluster: Ledger says it “progressed in our investigation into reports of a few tampered units in Germany,” and that those units were localized to Berlin. The company does not give a count for Berlin, so “a few” is the only quantity on the record.

The United Arab Emirates is the least settled of the three. Ledger writes that it is investigating reports of two tampered units in Dubai and is working with distribution partners to establish how those devices entered circulation. Two units under investigation is twice the number of confirmed devices in Southeast Asia, but the company does not call them confirmed, and its wording leaves the count open: no serial range, no purchase channel, no retailer named.

Ledger also expects the list to grow. The update says it “expects it is possible that additional devices will be found,” and adds that more are likely to surface through its own investigation and through social media reports from users.

Berlin Moves the Story Beyond One Region

The October disclosure was framed as a distribution-channel problem in a single part of the world. A criminal group, Ledger said at the time, targeted the end of the distribution chain and fitted genuine devices with hidden components before they reached a small group of users, working through resellers in Southeast Asia.

A localized cluster in Berlin breaks that containment story in two ways. It puts confirmed tampered inventory inside the European Union, where the devices would have passed through different distributors, different retail channels and different customs treatment than the Southeast Asian stock. It also moves the earliest relevant purchase date back to January 2026, months before the public disclosure, which means devices bought in the first ten months of the year remain in scope regardless of when the owner learned about the incident.

Ledger has not said whether the Berlin units arrived through the same reseller network, whether they were sold in stores or online, or how many were sold before the channel was reviewed. Those gaps are the difference between a contained batch and a wider distribution problem, and the company has not closed them.

The Implant Captures the Phrase, Not the Chip

The technical claim Ledger repeats in this update is the same one it made in October: “There is no flaw in Ledger’s secure chip or operating system, and no confirmed case involving a device bought on ledger.com.” The added hardware sits outside the secure element, which is why a compromised unit can still present as a working, correctly branded device.

That framing explains the remediation advice, which is unusually blunt about what to assume once a device is suspect. Ledger tells users not to use a doubtful device to set up or restore a wallet, to move funds to a wallet whose recovery phrase was generated on a device bought directly from ledger.com, and warns explicitly: “Do not reuse your current recovery phrase or passphrase, because a tampered device can capture both.”

The passphrase warning is the operational detail worth isolating. A passphrase is normally treated as a second layer that protects a wallet even if the 24-word recovery phrase is exposed, because the phrase alone does not open the passphrase-protected wallet. Ledger is telling affected users that this second layer should be considered compromised too, since the implant is positioned to capture whatever is typed into the device during setup.

The company has also kept the rules it imposed on its authorized network in October: no devices left on shelves or displays, hand-over at the point of purchase, no resale of returned devices, and prompt reporting of unusual products. It adds that where inspection is ongoing, resellers have been asked to pause sales.

Why the Fix Is Physical, Not Software

The remedy Ledger is offering for worried owners is a factory inspection, not a firmware check. For a limited period, its support team can arrange a physical examination that includes X-ray analysis, with the device shipped to Ledger’s factory in Vierzon, France for inspection and return.

That choice of remedy is the clearest signal in the document about what can and cannot be verified remotely. Ledger does not say whether any in-app or software test can identify the added component, and the fact that the escalation path runs through X-ray imaging suggests the answer is not a simple yes. For a buyer holding a second-hand or third-party device, the practical question is therefore not whether the device boots or connects, but where it came from and whether it has passed through a channel Ledger has cleared. Provenance has been the weak point elsewhere in the hardware wallet market this year as well: Keystone disclosed a website breach in October that exposed customer shipping data, the kind of record that tells an attacker where to aim a parcel.

The company also repeated the boundary that matters most for social-engineering risk: “Ledger will never ask for your 24-word recovery phrase, including Ledger Support, and will never ask you to send a device except through an official Support ticket.”

What the Singapore Record Already Shows About Losses

Loss figures in this campaign come from police, not from the vendor, and they are the only quantified harm on the public record so far. The Singapore Police Force advisory of 28 October 2026 reported at least two cases since 10 September with combined losses of about S$3.5 million, roughly US$2.7 million, from wallets bought at some retail stores in the city-state. The advisory said preliminary investigations indicated the devices could capture a buyer’s recovery phrase, and it was the first official confirmation that tampered units had reached retail shelves in Singapore rather than only online resellers.

Dividing that total by the two reported cases gives an average of about S$1.75 million per case, or roughly US$1.35 million at the exchange rate implied by the police figures. Two cases is a thin sample and an average of two data points is not a distribution, but it does establish the order of magnitude: these are seven-figure losses per device, not retail-scale theft.

What the record does not establish is a link. The police advisory did not name a supplier, and Ledger’s November update does not reference the Singapore cases, the S$3.5 million figure, or any confirmed loss in Berlin or Dubai. The two documents describe overlapping geography and the same method without a published bridge between them, and treating them as one confirmed chain of causation goes beyond what either source says.

What an Owner Should Check, and in What Order

The order of operations matters more than the checklist, because a device that has already been used to generate a phrase cannot be made safe by later inspection. Ledger’s guidance sequences it as follows: do not set up or restore on a suspect device; create a new wallet on a device bought directly from ledger.com and move funds there; do not reuse the old recovery phrase or passphrase; stop using the device and file a claim with local authorities; then open a support ticket through ledger.com.

Ledger’s own channel advice narrows the population that needs to act. Devices bought directly from ledger.com are excluded from the confirmed cases, per the company’s statement, which leaves third-party purchases in Southeast Asia, Berlin from January 2026, and Dubai as the groups it names. Owners outside those groups are not covered by a specific warning in this update, though the company’s general advice to verify provenance still applies.

What Ledger Has Not Said

Five gaps stand out in the 19 November text, and each one would change how the incident should be read.

The first is the Berlin count. “A few” is not a number, and without one there is no way to size the German cluster against the single confirmed unit in Southeast Asia or the two suspected units in Dubai.

The second is whether any Berlin or Dubai device was used to drain a wallet. The update reports device findings, not losses, and the only loss figures in public circulation remain the Singapore police numbers from October.

The third is the distribution route. Ledger says it is reviewing distribution records with partners and working with law enforcement, but it has not published which resellers handled the Berlin and Dubai units, or whether the same intermediary appears in more than one country.

The fourth is timing. The company says the investigation is active and that it expects more devices to be found, without a date for closing it or a trigger that would end the advisory.

The fifth is the relationship between this campaign and earlier tampering reports in the region. Ledger’s phrase “it is the same incident” covers the devices it has confirmed; it does not, on its own, establish that every tampered Ledger unit reported anywhere belongs to the same operation.

The practical reading for a holder is narrower than the headlines suggest and stricter than a routine firmware update. A genuine device with an added component defeats the assumption that authentic hardware is safe hardware, and the only verification Ledger currently offers for a doubtful unit is physical inspection at its own factory. Until the company publishes a count for Berlin, a channel list for Dubai, or a closure date, the useful signal for owners is provenance: where the device was bought, and whether that seller is one Ledger has cleared.

This article is not investment advice. It reports a vendor advisory and a police advisory as published on 19 November 2026 and 28 October 2026 respectively; owners of affected devices should confirm current guidance directly with Ledger Support.

The post Ledger Confirms Tampered Wallets in Berlin as Two Dubai Units Join the Probe appeared first on BlockchainReporter .

Disclaimer: This article is copyrighted by the original author and does not represent MyToken’s views and positions. If you have any questions regarding content or copyright, please contact us.(www.mytokencap.com)contact
More exciting content is available on
X(https://x.com/MyTokencap)
or join the community to learn more:MyToken-English Telegram Group
(https://t.me/mytokenGroup)