Crypto Theft: What the $106M Transfer Trail Reveals
A suspected $106M crypto theft and a separate Solana bot drain raise questions about tracing, wallet security and what on-chain evidence can actually prove.

Two Suspected Crypto Thefts Show the Limits of On-Chain Investigation
A suspected theft of more than $106 million from cryptocurrency exchange accounts, followed by reports of a separate $786,000 loss tied to a Solana trading bot, highlights a recurring problem in crypto investigations: suspicious transactions can show up on a blockchain long before anyone can confirm who's behind them - or even whether a wallet was actually compromised.
Blockchain investigator ZachXBT said an unidentified entity in the European Union may have lost funds withdrawn in USDC and USDT from accounts at multiple exchanges. The money was then reportedly moved through other cryptocurrencies and services, including conversions into Monero. Separately, the monitoring account Onchain Lens flagged rapid transfers from a wallet associated with the Solana arbitrage bot King. At the time of the report, King's operator had not confirmed a compromise.
These are two separate incidents. And neither one should be treated as fully verified based on transaction patterns alone. Below is what investigators reported, how cross-chain fund movements are typically interpreted, what those signals can - and can't - prove, and what exchanges and wallet operators can do when they suspect trouble.
What is known about the suspected $106 million theft?
ZachXBT reported that an unidentified entity in the European Union may have lost more than $106 million after funds were withdrawn from accounts at multiple cryptocurrency exchanges. The entity and the exchanges involved were not publicly named, and the alleged attacker has not been identified.
In ZachXBT's account, the funds were withdrawn in USDC and USDT - both dollar-pegged stablecoins - then exchanged and routed across assets and blockchains. The reported route included swaps from USDC into Ether, the use of instant exchange services such as WellWallet and Kyrrex, and conversion into Monero through the swap service Wagyu. ZachXBT also identified 11 wallet addresses tied to the suspected funds.
This kind of routing is common in large thefts. Victim funds often get split, swapped, consolidated, and moved across networks before they reach a destination. Each step complicates monitoring and recovery, while also giving investigators more points to examine. Still, a visible trail doesn't automatically identify who controlled each address or explain how access was obtained.
ZachXBT also said the movement of funds appeared to point away from a connection to North Korea's Lazarus Group. That's an investigative assessment, not a confirmed attribution. The report also came after a separate Binance hack reported on October 29, which the FBI attributed to North Korean hackers known as TraderTraitor, a group linked to Lazarus. The amounts and timing make both incidents relevant to the broader security discussion, but the available information doesn't establish that they're connected.
What remains unconfirmed
Several key details are still missing from the public reporting:
- The identity of the EU entity and the exchanges involved.
- How the attacker allegedly gained access to the accounts.
- Whether the funds were stolen through compromised credentials, social engineering, an insider, or another method.
- Whether any service froze or recovered assets.
- The identity of the person or group controlling the destination wallets.
Because of these gaps, the report should stay focused on what's actually supported by the evidence. "Suspected theft" is the safer phrasing than a definitive claim about the attacker or the method. A blockchain record can show that assets moved between addresses. It can't, by itself, confirm who authorized those transactions - or why.
How do investigators trace funds across crypto networks?
Investigators typically start with transaction data: addresses, amounts, timestamps, tokens, and the contracts or services involved. On public networks, those details can be used to build a timeline and map how assets moved. Investigators may then cross-check that activity against known exchange deposit addresses, service behavior, and other supporting evidence to narrow down leads.
In this case, the reported route crossed multiple asset types and networks. Stablecoins were allegedly converted into Ether, moved through instant exchange services, and eventually converted into Monero. Each swap or cross-chain step adds another layer to the analysis. Investigators have to determine whether assets on one network correspond to assets on another, whether a service pooled transactions, and whether a given address is controlled by a person, an exchange, or a contract.
The address-versus-identity distinction is crucial. A wallet address is a transaction endpoint, not a real-world name. If funds reach a centralized service, that service may be able to connect the activity to customer records - depending on what it has, and what legal process is followed. If funds move through self-custody wallets or privacy-focused systems, attribution can become harder. Either way, public visibility doesn't automatically mean universal access to identity data.
Why rapid swaps and cross-chain movement draw attention
Quick conversions and transfers across networks can look like an attempt to make tracing harder. Onchain Lens described the King-related movements as rapid, saying funds moved through several Solana wallets before being transferred to Ethereum using Mayan. The account interpreted this pattern as suggesting an attempt to obscure the origin of funds and a possible wallet compromise.
That can be a reasonable lead - but it's not proof on its own. Arbitrage systems often move assets between markets and networks as part of their normal operation. What looks odd from the outside may have a straightforward operational explanation, especially without access to the bot's strategy, transaction logs, or wallet controls. Investigators generally have to compare the activity against the wallet's baseline behavior and look for confirmation from the operator.
Monero adds another complication. It's designed to make transaction details less traceable than on more transparent blockchains. Converting into a privacy-focused asset can reduce what outside observers can follow, even though the visible conversion point may still provide an investigative clue. The outcome depends on what transaction records exist, how much cooperation investigators get from services, and what evidence is available beyond the chain.
A useful way to think about it is: signal, attribution, confirmation. A suspicious pattern is a signal. Connecting addresses or services to a real actor is attribution. Confirming what happened - and whether funds were actually stolen - requires evidence from the affected organization, platforms, incident response teams, or law enforcement. Skipping steps leads people to sound certain about things the data doesn't fully support.
What does the Solana bot report tell us about wallet risk?
King is described as an automated Solana arbitrage bot - software that tries to buy an asset on one market and sell it on another to capture a price difference. That kind of setup often involves frequent transactions and movement between wallets. It also creates a specific operational risk: if a wallet holds trading capital or is used to execute automated trades, it becomes a high-value target.
Onchain Lens said a wallet associated with King may have lost about $786,000. It reported that funds moved through several Solana wallets and then to Ethereum via Mayan, a cross-chain service. The monitoring account told Cointelegraph that the speed and cross-chain movement suggested a possible compromise. At the time of the report, the bot's operator had not confirmed that its wallet was compromised.
That qualification matters. A wallet connected to a bot isn't automatically proof that the bot itself was hacked. Funds could have been moved by an authorized operator, through a compromised key, due to a misconfiguration, or for other reasons. Without confirmation from the operator and a review of the wallet's access controls, observers can't reliably tell those scenarios apart.
Automation changes the consequences of a key compromise
With a manually managed wallet, a person often has to approve transfers. With automated trading, software or a server may have ongoing authority to move funds. If a signing key sits in an exposed environment, an attacker may be able to move money quickly - before a human notices. Automation can improve execution speed, but it also raises the stakes of restricting what any single key can do.
A more controlled setup often looks like this:
- Keep only the funds needed for active trading in a hot wallet.
- Store reserves separately, with stronger approval requirements and limited access.
- Restrict keys to specific contracts, amounts, or transaction types where the system allows it.
- Monitor outbound transfers and pause automation when activity exceeds defined thresholds.
- Use a tested process for rotating keys and disabling compromised credentials.
Those controls aren't free. More approvals can slow trading and add operational overhead. Tighter limits can also interfere with a legitimate strategy during volatile markets. The goal isn't to eliminate every risk. It's to make sure one compromised credential can't trigger an uncontrolled loss.
What should exchanges and wallet operators do after a suspected theft?
For an exchange or affected organization, the first priority is containment, not public attribution. Teams need to identify which accounts, credentials, and systems might be exposed, stop further unauthorized withdrawals where possible, and preserve evidence. That can include suspending compromised sessions, resetting credentials, reviewing API keys, and escalating suspicious activity to relevant service providers.
Incident response also depends on speed and usable records. Teams should preserve timestamps, transaction hashes, account access logs, approval history, and communications with exchanges. A clean timeline helps analysts reconstruct what happened and gives platforms or law enforcement something concrete to evaluate. When organizations speak publicly, they should separate observed facts from working theories - overstating what's known can confuse customers and complicate the investigation.
Exchanges have a tricky balancing act. They may be able to flag or restrict suspicious deposits inside their systems, but they can't assume every flagged transfer is illicit. Freezing funds can disrupt legitimate users, while slow escalation can leave too little time to stop money moving quickly. That's why decisions should be driven by documented criteria, a clear escalation path, and appropriate legal review.
A response checklist for operators
When a wallet or exchange account might be compromised, a practical sequence is:
- Contain access. Revoke suspicious sessions, rotate exposed credentials, and disable affected keys or automated jobs.
- Protect remaining assets. Move funds only through a verified, preplanned process; avoid improvised transfers that introduce new errors.
- Build the timeline. Document the first known unauthorized action, account changes, approvals, and relevant transaction identifiers.
- Notify counterparties. Contact exchanges and services that may receive funds, using specific addresses and transaction details rather than broad claims.
- Preserve evidence. Keep logs and communications in a controlled record so responders can work from the same facts.
- Communicate carefully. Say what's known, what's suspected, and what remains under investigation.
- Review the control failure. After containment, identify whether the issue involved credentials, permissions, software, personnel, or a third-party service.
This order is meant to be operational. A detailed attribution report can come later. The immediate objective is to stop more loss, preserve evidence, and give the right services enough information to act. For teams operating across multiple chains, that process is something you rehearse before an incident - not build on the fly.
Conclusion
The reported $106 million loss and the separate Solana bot movements point to a basic divide: blockchains can make transfers visible, but visibility doesn't automatically prove who made the transfers, why they happened, or whether funds can be recovered. Investigators can use transaction patterns to build leads, but affected organizations still need to verify what happened, contain access, and preserve evidence.
For exchanges and automated trading teams, the practical takeaway is straightforward: limit what any one account or key can do, watch behavior against a known baseline, and rehearse a fast containment process. Treat on-chain alerts as early warning signs - not as the final verdict.