Crypto Theft: What the Suspected $106M Loss Reveals12 min read2,346 words

Crypto Theft: What the Suspected $106M Loss Reveals

A suspected $106 million crypto theft shows how stolen funds move across exchanges and chains—and why response speed, attribution and controls matter.

crypto theftcrypto hackstablecoin launderingMoneroexchange security
Crypto Theft: What the Suspected $106M Loss Reveals

A Suspected $106 Million Crypto Theft, Explained

A suspected loss of more than $106 million from accounts tied to an unnamed European Union entity is a useful case study in how crypto theft response works - and why it's often harder than it looks. On-chain investigator ZachXBT said the funds were taken from several centralized exchanges in USDC and USDT. The victim and the attacker haven't been publicly identified, and the exact way the accounts were compromised hasn't been disclosed.

The reported moves after the withdrawals matter just as much. ZachXBT said the suspected thief swapped stablecoins for ETH, used instant exchange services, converted part of the flow into Monero, and bridged assets across blockchains. Each step can make tracing more time-consuming, but it doesn't automatically make funds impossible to follow - or prove that laundering succeeded. Still, it can compress the time available for exchanges, stablecoin issuers, and investigators to act.

This article pulls together what's been reported, why the route matters, how stablecoin controls can affect incident response, and what institutions can learn without pretending the missing details are known. In fast-moving incidents, it's tempting to run with confident headlines - but it can get ahead of the evidence.

What happened in the $106 million crypto theft?

ZachXBT reported that an unnamed entity in the European Union may have lost more than $106 million from multiple accounts on centralized exchanges on November 1. The funds were withdrawn as USDC and USDT. ZachXBT also published 11 Ethereum addresses associated with the suspected theft and described the responsible party as an illicit actor.

That's the shape of what's visible in public - but it isn't a full incident report. The victim's identity, the exchanges involved, the method of account compromise, and the exact amount ultimately controlled by the attacker haven't been disclosed in the source reporting. So it's more accurate to describe this as a suspected loss than to treat every detail as settled.

What is known - and what is not

From what's been described publicly, the incident starts with withdrawals from exchange accounts. But that doesn't tell us whether the attacker used stolen credentials, compromised email, a compromised device, insider access, social engineering, or something else. Those are all plausible paths in general, but there's nothing here that supports choosing one over the others.

That distinction matters if you're trying to learn from the incident. If the entry point was weak account recovery, then improving withdrawal controls might help. If a device or corporate identity system was compromised, the right fixes would look different. With the missing incident details, the useful takeaway isn't "use tool X." It's that organizations with meaningful exchange balances need controls across identity, approvals, devices, and withdrawal operations.

The reporting also places the theft in a rough period for crypto security. It came after the separate, record-setting $6.4 billion Binance hack. In that case, the FBI attributed the attack to the North Korean hacking group TraderTraitor. A Brazilian exchange, Mercado Bitcoin, also said it halted withdrawals after a separate $40 million hack, and BTCPay Server warned merchants about hot-wallet attacks. Still, these events shouldn't be lumped together: similar timing doesn't prove a shared attacker or a shared cause.

Why the attribution is still uncertain

ZachXBT said - using a "high degree of confidence" - that the EU case wasn't carried out by Lazarus Group, the umbrella name often used for North Korea's state-backed hackers. He pointed to laundering indicators, but he didn't publicly name the suspected attacker or the victim. That's an investigator's assessment, not a formal law-enforcement attribution.

For operators, the practical point is simple: start with transaction and account evidence, not assumptions about who did it. Attribution can matter later for enforcement and sanctions work, but waiting for it can cost time - time in which funds might still be frozen or contained.

How did the suspected thief move the funds?

ZachXBT said the actor moved quickly after the initial withdrawals. The reported route included swapping USDC for ETH, sending funds through instant exchange services such as WellWallet and Kyrrex, converting some of the assets to Monero through Wagyu, and bridging assets across multiple blockchains.

This isn't a "magic invisibility" playbook. Conversions change where analysts need to look and which companies or networks may have relevant records. They also create real work for responders: mapping addresses, matching transactions across chains, identifying service touchpoints, and contacting the right platforms before records become harder to obtain - or funds move again.

Why use swaps, instant exchanges and bridges?

Swapping one token for another can break a straightforward trail that relies on a single asset. Bridging moves value between blockchain networks, which means responders have to follow activity on both the source chain and the destination chain. Instant exchange services can also add counterparties and operational handoffs along the way.

These services vary in how they operate and what they collect. It would be a mistake to assume every instant exchange has no identity checks, or that using one automatically means funds can't be traced. Service policies, jurisdictions, liquidity arrangements, and available records all differ. The presence of a service name in a transaction trail is useful for investigators, but it doesn't tell you exactly what information the service had - or what it could share.

Monero adds another layer of complexity. It's a privacy-focused cryptocurrency designed to obscure transaction details, including sender, receiver, and amount. Once funds are converted into a privacy coin, public-chain analysis may offer less visibility than it does with more transparent assets. That makes timing and coordination more important - especially before a conversion happens. But it still doesn't prove that all stolen funds were converted to Monero or that the entire flow was successfully concealed.

Why speed changes the response

A response team has to do multiple things at once: preserve exchange account records, identify the withdrawals, map addresses, alert relevant platforms, and check whether issuers can take action on tokens still under their control. A purely sequential approach - finish the investigation first, then notify counterparties - can burn the clock when it matters most.

The reported route also shows why watching only the first withdrawal isn't enough. The trail can continue through swaps, bridges, and new wallets. Organizations should preserve transaction identifiers and timestamps at each step, while analysts keep a clear line between what's observed and what's inferred about control. The goal isn't to claim certainty from a partial trail; it's to give counterparties precise, actionable information quickly.

Why do stablecoin freezes matter?

USDC and USDT are stablecoins issued by companies that can, under certain conditions, freeze tokens at specific addresses. That makes them different from assets without a centralized issuer that can act at the token-contract level. If stolen stablecoins stay at an address the issuer can freeze, then fast, credible reporting may help restrict further movement.

In the separate Binance case, stablecoin issuers reportedly acted quickly. According to the source reporting, Tether froze stolen USDT on Ethereum within 37 minutes, and Circle froze the reported $823 million in stolen USDC. Elliptic said those actions helped lock up about 44% of the haul. That's an example of what's possible - not a guarantee that issuers will recover every stolen token, or that the same outcome applies in this EU case.

Freezing is a capability, not a recovery plan

A freeze can stop certain tokens from moving, but it doesn't undo the original theft or automatically return assets to the victim. It depends on factors like the token, chain, address, issuer policy, and the quality of the information responders provide. If funds have already been swapped, bridged, or converted into a privacy coin, a freeze may only cover part of the flow - whatever is still held in a form and location where issuer controls apply.

There's also a governance trade-off. The ability to restrict token movement can support compliance and incident response, but it also means an issuer has centralized powers that users of decentralized networks may not expect. Whether that's a feature or a risk depends on the use case. For a business managing treasury funds, a timely freeze can be genuinely useful. For a user prioritizing censorship resistance, issuer intervention is part of the asset's trust model - and it should be understood up front.

Why moving out of stablecoins can be a strategic choice

The reported conversion from USDC and USDT to ETH is significant because it changes what control an issuer can apply. A stablecoin issuer may be able to freeze tokens at an address, based on its systems and policies. ETH doesn't have an equivalent central issuer with the same token-freezing mechanism. ETH can still be traced, but the available intervention options are different.

The practical lesson for institutions isn't to assume a freeze will happen. Plan for issuer contacts and a process for sharing clear evidence - but also prepare for cases where funds have already moved beyond issuer control. Incident response needs both technical tracing and operational coordination; one doesn't replace the other.

What should exchanges and institutions learn?

The public information doesn't explain how the accounts were compromised, so it can't support a narrow conclusion about one specific security failure. What it does support is a broader operational lesson: high-value exchange balances need controls that reduce both account takeover risk and the speed at which a compromised account can empty funds.

For an institution, the relevant system is bigger than the exchange login. It includes identity providers, email, endpoints, approval workflows, API keys, withdrawal address management, and the people authorized to act. A weakness in any one part can undermine controls elsewhere. Strong authentication helps, but it won't compensate for an attacker who can change recovery details - or persuade an approver to authorize a withdrawal.

Build controls around the withdrawal path

A practical baseline for organizations holding material exchange balances includes:

  • Separate access from approval. The person who initiates a withdrawal shouldn't also be the only person who can approve it. How many approvals you need should depend on the amount and the business context.
  • Use withdrawal allowlists and change delays. Limit withdrawals to reviewed addresses where the exchange supports it. Treat changes to an allowlist as high-risk events, and use independent verification plus a waiting period when possible.
  • Set limits that match normal operations. Daily caps and transaction thresholds can slow an attacker without making routine treasury work impossible. Review them against actual withdrawal patterns, rather than picking a limit staff will bypass.
  • Protect account recovery and API access. Secure email and identity-provider accounts, inventory API keys, remove unused credentials, and alert on permission changes. Recovery paths often deserve the same attention as the primary login.
  • Monitor for unusual activity. Escalate on signs like new devices, changed withdrawal details, off-hours access, and rapid asset conversion. Alerts only help if someone owns the process - and has authority to pause activity.

Prepare for the first hour, not just the postmortem

A response plan should name decision-makers and lay out how containment will happen. Teams need to know who can freeze exchange activity, who can contact an issuer, who preserves logs, and who communicates with law enforcement or outside investigators. One incident lead should coordinate facts so different teams don't send conflicting or incomplete information.

It also helps to rehearse the plan under realistic constraints. Can a finance lead reach the exchange incident channel without using an email account that might be compromised? Can the team identify which wallets and accounts belong to the company? Can two approvers stop an outgoing transfer while preserving evidence? These are operational questions, not "policy document" questions.

Finally, don't treat public address lists as proof of control. They can be useful indicators, but analysts and organizations should verify what they correspond to and preserve the basis for any claim. Accurate, timestamped information is more valuable to a platform - and less likely to create avoidable mistakes during a fast-moving response.

Conclusion

This suspected $106 million EU loss shows why crypto incident response is a race across accounts, assets, services, and blockchains. Swaps, bridges, and privacy coins can complicate tracing, while stablecoin issuers may have limited - but time-sensitive - tools to restrict movement. A public address list or early attribution still doesn't settle the full story.

For institutions, the actionable response is to reduce the chance that one compromised account can move a large balance, and to rehearse what happens immediately after an alert. Separate approvals, tightly managed recovery paths, withdrawal controls, and a clear escalation plan aren't guarantees - but they buy time. And in an incident involving rapidly moving funds, time can determine what options remain.

Frequently Asked Questions

The reporting describes a suspected loss of more than $106 million from accounts belonging to an unnamed EU entity. ZachXBT reported the incident and identified associated addresses, but the victim, attack method and final amount have not been publicly confirmed in the available account.
The attacker has not been identified publicly. ZachXBT said with a high degree of confidence that the activity was not linked to Lazarus Group, citing laundering indicators. That is an investigator’s assessment, not a formal law-enforcement attribution.
Their issuers can freeze tokens at certain addresses under applicable processes and policies. Whether that is possible depends on the token, chain, timing and location of the funds. A freeze may restrict movement, but does not automatically recover assets.
Monero is designed to obscure transaction details, which can make public-chain tracing more difficult. But conversion does not prove all stolen funds entered Monero or that investigators have no other evidence. Records and activity before conversion may still provide leads.

Related articles