Mercado Bitcoin Hack
The attacker-linked wallets, labelled and maintained by Chainlabs
Read more
Following the Bitget funds with an AI agent
In short: On 24 September, attackers took about $387 million from Bitget's hot wallets across seven blockchains, and the money has since been swapped into Bitcoin and spread across thousands of new wallets. Investigators following it are leaning on AI agents because no team can watch that many wallets by hand. But an AI agent can only take them so far. To turn a trail into a frozen account, it has to know who is behind each address it reaches. The funds are expected to move slowly through OTC desks, mixers and regional exchanges, where Chainlabs covers more than 2,000 OTC desks and 800 regional exchanges.
Bitget's CEO has linked the attack to North Korean groups, and the exchange is offering a 5% bounty for help recovering or freezing the funds.
The scale is the problem. We spoke to a Chainlabs analyst who has followed the Bitget funds since day one. "The complexity of this case is the number of wallets," he says. "You cannot do it manually." The attackers also send funds back and forth between wallets to break the trail, so an alert on a single address goes quiet after one hop.
His answer is an AI agent of his own, which follows the funds across all of those wallets at once. Which model it runs on matters less, he says, than the data it can reach.
The attackers cannot move this much at once without being noticed, and the sum is too large to swap into a privacy coin such as Monero, which does not have the liquidity to absorb it. For now, most of the Bitcoin is idle, and in the first weeks, the attackers stayed away from exchanges altogether. So the funds are expected to move slowly, in smaller pieces, through OTC desks, mixers and regional exchanges.
That is where this kind of case is won or lost. Exchanges and OTC desks hold customer accounts. When stolen funds reach one, there is a business that can freeze them and knows who the customer is, but only if the investigator learns quickly that the address belongs to one.
At every hop, the analyst's rules come down to one question: who is this? Each time a wallet moves, the AI agent reaches a new address and has to decide what to do with it.

Without the context of labelled wallets, the AI agent is blind. "Agents are capable of following the funds," he says. "The problem is they don't know what the address is." An AI agent that doesn't recognise an exchange keeps going straight through the exchange's own wallets and ends up following thousands of unrelated customers instead of the stolen funds.
"If you put trash information in, you get trash out," he says. "With a good feed of labels, it is the next level of tracing for the agent."
The gaps sit exactly where the Bitget funds are expected to go: regional exchanges and OTC desks, which few public tools identify. Free wallet labels are useful for a first look, and the big exchanges are well covered. This is where Chainlabs coverage is strongest: we cover more than 2,000 OTC desks and 800 regional exchanges, many identified first-hand by investigators. A miss there is not a small error. It is the freeze that never gets requested.
In a case of this size, an attribution also has to hold up. An exchange's compliance team or a regulator will ask where it came from, and a crowd-sourced label with no source cannot answer that.
Chainlabs identifies who is behind crypto addresses. Our network of investigators establishes many attributions first-hand, rather than inferring them from on-chain patterns alone. An estimated 90% of the KYT market runs on Chainlabs data, and our coverage is strongest where this case is heading: regional exchanges, OTC desks and darknet services.
Every attribution is supported by verifiable source evidence, and the data is updated daily.
Through the Chainlabs MCP server. So far, our data has been available mainly through the largest compliance platforms. We are now making it available to investigators and builders directly, starting with a small group of design partners. MCP (Model Context Protocol) is the standard way to connect an AI agent to a data source, so there is no new software to learn. You add the Chainlabs MCP server to Claude, or any AI agent that supports MCP, and it can ask who is behind an address, or check a whole batch, at every hop of a trace. It starts with Bitcoin.
Become a design partner: If you trace funds with AI, or you are building an investigation tool and need attribution you can stand behind, we would like you to test it for free and tell us what is missing.
👉 Email mcp@chainlabs.ai
Chainlabs identifies who is behind cryptocurrency addresses. Investigators and compliance teams use its attribution data, and it sits behind several leading compliance platforms.
It connects Chainlabs attribution data to AI agents through the Model Context Protocol. An AI agent can ask who is behind a Bitcoin address, or check a batch of addresses, and get the entity, its category and the date of the data.
Any AI agent or client that supports MCP, including Claude.
Every attribution is supported by verifiable source evidence. Coverage is strongest for regional exchanges, OTC desks and darknet services, which free tools rarely identify.
It says so, with the date of the data and our overall coverage. It never guesses, and never calls an address clean.
It starts with Bitcoin. Chainlabs covers more than 30 blockchains, so tell us which one you would most like added next.
It is updated daily.
Email mcp@chainlabs.ai. Testing starts with Bitcoin and is free during the test period.
Want to use this data in your own investigations? Book a call with our team.
The attacker-linked wallets, labelled and maintained by Chainlabs
Read moreCan you trust your AI agent’s data?
Read moreHow much you can trust a label depends on how it was made.
Read more