ZachXBT Flags Lazarus As Top Kruw CoinJoin User

10 min read
1 views
Nov 17, 2026

ZachXBT just called out a CoinJoin operator for allegedly serving North Korea’s Lazarus Group as its biggest user. Hundreds of millions in stolen Bitcoin moved through privacy rounds. The numbers raise hard questions about who should carry responsibility next.

Financial market analysis from 17/11/2026. Market conditions may have changed since publication.

I’ve been watching privacy tools in Bitcoin for years, and every so often a single post drops that forces the whole conversation back into the open. This week it happened again. An on-chain investigator publicly questioned a CoinJoin coordinator after the operator highlighted how much blockspace his users were consuming. The reply was blunt: the biggest “user,” according to the investigator, looks a lot like North Korea’s Lazarus Group moving hundreds of millions in stolen coins.

That claim landed hard because it sits at the uncomfortable intersection of privacy, crime, and open-source software. CoinJoin exists to break the easy links between inputs and outputs. When a well-known state-linked hacking crew appears to lean on one particular coordinator more than anyone else, people start asking whether the operator should have known, whether he bears any responsibility, and where the line sits between neutral infrastructure and knowing facilitation.

What Sparked The Latest Exchange

The sequence began with a public note from the coordinator known as Kruw. He pointed out that users of his service had accounted for a noticeable slice of overall Bitcoin blockspace. Earlier figures put the share around 1.1 percent; the newer claim pushed it to 1.6 percent. No clear measurement window or exact methodology appeared alongside the numbers, which left room for interpretation.

Within hours the investigator known as ZachXBT replied. He suggested the operator was celebrating volume while fully aware that the largest single source of that volume was Lazarus laundering proceeds from major exchange exploits. He attached tracking data that showed large amounts of Bitcoin flowing from wallets linked to the Bitget incident into CoinJoin rounds.

The accusation did not come with a customer ranking table or a perfect one-to-one mapping of every coin to that single coordinator. Still, the timing and the volume made the point land. In crypto circles the combination of a public percentage claim and a high-profile investigator’s response is enough to keep the discussion alive for days.

The Scale Of The Tracked Flows

Independent analytics painted a concrete picture. Over an eleven-day window, wallets labeled as belonging to the Bitget attacker sent out more than 2,266 Bitcoin, valued at the time around 161 million dollars. Roughly 95 percent of those outflows entered CoinJoin transactions. Of the CoinJoin total, the majority went straight into WabiSabi rounds while a smaller portion first touched fresh addresses.

Daily movement varied. Some days saw more than 300 Bitcoin leave the labeled set. By the later reporting cutoff only a few dozen Bitcoin remained visible in the original wallets. Analysts noted that additional funds could still sit in unlabeled addresses controlled by the same party, and that over-the-counter desks or other services remained possible exit routes.

These numbers matter because they show concentrated use of collaborative transactions rather than scattered, low-volume activity. When one cluster accounts for such a large share of a coordinator’s apparent traffic, questions about awareness become harder to dismiss.

How CoinJoin Actually Works In Practice

For anyone less familiar with the mechanics, a quick refresher helps. In a standard Bitcoin transaction the inputs and outputs create a relatively clear ownership trail. CoinJoin changes that by letting multiple participants contribute inputs and receive outputs in a single collaborative transaction. The goal is to make it statistically harder for outside observers to match which input belongs to which output.

WabiSabi is one of the more recent protocols used for these rounds. It supports unequal amounts and more flexible participation compared with earlier equal-amount designs. Coordinators help organize the rounds, collect registrations, and broadcast the final transaction. They do not take custody of the coins in the classic sense, yet they sit in a privileged position to see who is trying to join and how often.

That visibility is the heart of the current debate. A pure peer-to-peer design with no central organizer would look different. Once a single entity repeatedly facilitates large rounds, patterns become visible to both the operator and to external investigators who monitor the chain.

Earlier Warnings From Authorities

This is not the first time the same service name has appeared in official materials. A government alert issued the previous year specifically named the coordinator’s domain among tools used by Lazarus. The alert described prior mixing of roughly fourteen million dollars and noted ongoing use in connection with proceeds from a much larger exchange theft.

The same document characterized the service as one of the more active remaining coordinators after an earlier well-known provider shut down its coordination function. That shutdown itself had been driven by regulatory pressure and by the operator’s decision to stop supporting the feature rather than risk further legal exposure.

In my view the repeated appearance of the same name across both private investigations and public alerts raises the practical question of whether continued high-volume operation without stronger filters is sustainable. Privacy advocates will argue that any restriction undermines the tool for legitimate users. Enforcement-minded observers will counter that ignoring clear patterns of illicit use invites the same outcome that already hit other mixing services.

Lessons From Recent Enforcement Actions

Recent court outcomes against other privacy-tool operators provide a useful backdrop. Founders of a different mixing wallet pleaded guilty to operating an unlicensed money-transmitting business and to transmitting hundreds of millions in criminal proceeds. Prison terms, supervised release, large fines, and forfeiture of fees followed.

Prosecutors emphasized active marketing to criminal users and encouragement of stolen-fund deposits. The legal theory did not require the operators to have stolen the coins themselves. Knowledge and facilitation were enough.

Those cases sit in the background of every new accusation. Coordinators who continue operating after public alerts and after large volumes from labeled hacker wallets become visible on-chain are taking a calculated risk. Some will decide the risk is acceptable. Others will tighten controls or exit the coordination role entirely.


The Accountability Question

Should a coordinator be held responsible when a state-linked group becomes its largest apparent customer? The answer depends on what one believes about the nature of the service.

One camp treats CoinJoin coordination as pure infrastructure, comparable to a road or a telephone network. In that framing the operator provides a technical service and should not be expected to police every participant. Demanding otherwise, they argue, simply drives activity underground or into less transparent tools.

The opposing view holds that once an operator can see repeated large inflows from addresses already flagged by multiple independent trackers, continuing without friction starts to look like willful blindness. Public statements celebrating high blockspace usage while those flows are ongoing only strengthen the perception of indifference.

I’ve found that most people who work day-to-day with on-chain data land somewhere in the middle. They accept that perfect knowledge is impossible and that false positives can harm ordinary users. At the same time they struggle with the idea that a single service can absorb hundreds of millions from the same labeled cluster without any operational response.

Privacy Versus Traceability Trade-Offs

Bitcoin’s design already sits in tension between transparency and privacy. Every transaction is public, yet the pseudonymous nature of addresses gives users a layer of separation. CoinJoin tries to thicken that layer. When sophisticated actors exploit the same layer, the political pressure to thin it again increases.

Protocol-level privacy improvements have been discussed for years. Some developers argue that stronger base-layer privacy would reduce the need for specialized coordinators and the regulatory targets they create. Others note that meaningful protocol changes take time and face their own adoption hurdles.

In the meantime the practical reality is that a handful of remaining coordinators carry a disproportionate share of the privacy load. That concentration makes each of them a more attractive target for both investigators and for the criminal groups seeking to move volume.

What The Numbers Suggest About User Composition

When an operator claims users of his service consume more than one percent of total blockspace, the composition of those users becomes relevant. Ordinary privacy-conscious individuals rarely generate that kind of sustained throughput. Institutional or high-volume actors do.

The analytics showing thousands of Bitcoin from a single labeled cluster entering rounds over a short window support the investigator’s characterization. Even if the exact ranking of “largest user” cannot be proven to the last satoshi, the scale is large enough to dominate any reasonable distribution of legitimate traffic.

Perhaps the most interesting aspect is how little the public conversation has focused on the remaining small balances still visible in the original wallets. Analysts left open the possibility that additional coins sit in fresh addresses or have already moved through other channels. The story is therefore incomplete by design, which is typical of on-chain investigations that rely on public data alone.

Broader Implications For Privacy Tool Operators

Every new high-profile case reshapes the risk calculation for people still running coordination services. Some will add stronger heuristics, rate limits, or manual review for large registrations. Others will simply keep the existing open model and accept the elevated legal exposure.

The shutdown of earlier coordination services already demonstrated one path. When the perceived cost of continued operation exceeds the perceived benefit, the service ends. Users then migrate to remaining options, further concentrating the remaining traffic and repeating the cycle.

I keep coming back to the same practical observation: tools that deliver real privacy will attract both legitimate users and sophisticated adversaries. Designing systems that serve the first group without becoming the preferred rail for the second is harder than most whitepapers admit.

How Investigators Piece The Story Together

Modern on-chain analysis combines address clustering, timing patterns, amount heuristics, and known exchange deposit behaviors. When a set of wallets is already labeled through prior work, subsequent outflows become easier to follow. CoinJoin rounds complicate the trail but do not erase every signal.

In this instance the combination of labeled source wallets, large equal or near-equal outputs entering rounds, and the public statements from the coordinator created a coherent narrative. The investigator did not need to prove absolute knowledge on the operator’s part. Highlighting the apparent mismatch between the celebration of volume and the origin of that volume was enough to shift the discussion.

That approach has become common. Public pressure often arrives before formal legal process. Whether it produces operational changes or simply more careful public messaging varies from case to case.

Possible Paths Forward

Several options exist for the broader ecosystem. Stronger base-layer privacy features would reduce reliance on specialized coordinators. Clearer voluntary standards for operators could create a middle ground between pure openness and heavy KYC. Continued enforcement against services that ignore repeated red flags remains the default path in many jurisdictions.

None of these paths is free of trade-offs. Protocol changes require consensus and careful engineering. Voluntary standards are only as strong as the willingness of participants to follow them. Aggressive enforcement can push activity into less observable channels.

In the short term the most likely outcome is continued scrutiny of any coordinator whose volume statistics look outsized relative to known legitimate demand. Public claims about blockspace share will invite exactly the kind of response seen this week.

Why Ordinary Users Should Still Care

Most Bitcoin holders never touch CoinJoin. They still have a stake in how the debate resolves. If privacy tools become so tightly regulated or so heavily associated with crime that development stalls, the overall option set shrinks. If operators face no meaningful constraints even after repeated public links to major hacks, political pressure for broader restrictions on the entire ecosystem grows.

The healthy middle ground is hard to locate and even harder to maintain. It requires acknowledging that privacy is legitimate while also recognizing that certain patterns of use create real externalities. Pretending either side of that equation does not exist only prolongs the cycle of boom, exposure, and crackdown.

I’ve watched enough of these cycles to know that the next one is already forming somewhere. The specific names change. The underlying tension between open tools and adversarial use does not.

Looking At The Larger Pattern

Lazarus has a long track record of high-value exchange and DeFi exploits followed by careful layering through mixers, bridges, and over-the-counter desks. Each successful laundering path that remains available simply encourages the next attempt. When one path becomes too visible, the group shifts. The appearance of the same coordinator name across multiple alerts and investigations suggests that particular path stayed open longer than many expected.

Whether that longevity reflects technical resilience, limited alternatives, or insufficient operational response is a question only the people closest to the service can answer. From the outside the volume numbers and the investigator’s public challenge create a clear narrative that will be difficult to ignore.

The coming weeks will show whether the coordinator adjusts practices, whether users migrate elsewhere, or whether the conversation simply moves on until the next large labeled outflow appears. In crypto the latter outcome is always possible. The underlying questions about responsibility do not disappear with the news cycle.

At bottom this episode is less about one operator and one investigator than about the unfinished business of building privacy tools that can survive both technical and legal scrutiny. The blockspace percentages and the multi-million-dollar flows are simply the latest data points in a longer argument that shows no sign of ending soon.

Anyone who cares about the future of open financial tools has a reason to pay attention. The choices made around coordination services, disclosure of volume, and response to clear adversarial patterns will shape what remains available to ordinary users years from now. That is the real stake, far beyond any single week’s social-media exchange.

❝
Blockchain technology isn't just a more efficient way to settle transactions, it will fundamentally change market structures - perhaps even the architecture of the Internet itself.
— Abirgail Johnson
Author

Steven Soarez passionately shares his financial expertise to help everyone better understand and master investing. Contact us for collaboration opportunities or sponsored article inquiries.

Related Articles

?>