A $118,605 deposit address belonging to a Telegram black-market search bot. Nine outbound paths checked. Eight lead back into the same mesh. Seven hops later, one counterparty relationship handles $1.07 billion, and not a single node of it appears in either of the two most-used compliance databases in the industry.
It starts small, and it isn’t supposed to lead anywhere
超搜 (ChaoSou), Telegram bot @cszwbot, is a Telegram search bot with 105,789 monthly users. It indexes and monetizes access to money muling, counterfeit and compliance-flagged USDT, stolen-card fraud, KYC-bypass account farms, illegal gambling, and prostitution solicitation, all in one searchable directory, with its own built-in USDT wallet.
TBRdQCfUu33bSJziHWoj9QArxV82KVt4E5 is one of that wallet’s rotating deposit addresses. On its own: $118,605 processed, 550 senders, unremarkable by the standards of anything else we’ve documented in this investigation.
That should have been the whole story. It isn’t.
Every door out of this wallet leads back to the same building
We checked nine of TBRdQCfUu’s direct outbound recipients, expecting the scatter of unrelated addresses most wallets produce. Instead, eight of the nine tie back into the same small handful of anchor points. Five route significant money to the same confirmed OKX exchange hot wallet. Four independently touch one specific unlabeled address. Three touch another. Four transact directly with each other. This isn’t a wallet that happens to be adjacent to something bigger, it’s a wallet sitting inside a dense, pre-existing mesh from its very first hop.
FIG 1Convergence matrix: nine recipients against six recurring anchors
Filled cell = verified transfer relationship
Recipient
OKX
hot wallet
TS4Y9
AeZ5t
TDuty
PwkEwH
TZ29k
1iPA8
TKU7j
nAvN12t
TLxZm
8HJK
Ties
TMw4hJrYrHDYSJXEwVVrgbvuhgHZGHiAAQ
4
TPs3xXe6z28KzMKu2QrTvLq2CN7ztHRZMV
3
TYhNWA1VLKPT7w9JMcSTxX2sW4zfbK9NsU
6
TVqpWKbBYAJAM3sm3gnAz7i8o111111111
3
TDutyPwkEwHogyt1kJPYQQk3gP66S6U4h8
self
4
TA89c9d2dMtc1vnzS3hhrMZVTqoS7ChHVm
BNB
TAEsmyvam88kU7v7nwoiarnG73vJmveaTs
1
TQUqCq1og9YKVa3DmbrxBY5YPLzi14trqj
1
TALsXrymdLKpXYXzPDoeLddm8JPjLmygrk
0
Recipients touching this anchor
5
4
4
3
3
2
Confirmed exchange infrastructure, routine on its own
Unlabeled recurring anchor
No observed relationship
TMw4hJrYrHDYSJXEwVVrgbvuhgHZGHiAAQ
100%
of outbound, $204,655 across 30 transactions, goes to the confirmed OKX hot wallet. Fed by TS4Y9AeZ5t ($36,820) and TZ29k1iPA8 ($12,069), both recurring.
TYhNWA1VLKPT7w9JMcSTxX2sW4zfbK9NsU
$524,496
across 76 transactions, 91%+ of its outbound, straight to the OKX hot wallet. Fed by five separate anchors, the largest being TKU7jnAvN12t at $90,447.
TALsXrymdLKpXYXzPDoeLddm8JPjLmygrk · outlier
6,807
received transfers, 3,377 senders, 362 receivers. No anchor overlap in its top 15; dominant senders show “tron.ink” $1M–$10M spam-token noise. Flagged unresolved, not folded into the mesh.
Gather quietly from 2,187 directions, then sweep
One of those nine recipients is a vanity address ending in nine ones, TVqpWKbBYAJAM3sm3gnAz7i8o111111111, just six to seven weeks old, confirmed by binary-searching its actual transfer history rather than trusting a stale summary field that told us it was two and a half years older than it really is.
It collects from 2,187 senders, most of them small, unlabeled, dust-level contributors. Classic structuring: gather quietly from many directions, then sweep. It sweeps on a near-weekly schedule, in $96,000–$125,000 tranches, alternating between two wallets that were created on the exact same day and have barely moved money since. Textbook parking wallets.
FIG 2Many small in, two large out, on a near-weekly clock
1,093 senders per destination
Inbound · 2,187 senders
Each mark ≈ 18 senders. Dust-level, unlabeled, no exchange attribution.
…111111111
6–7 weeks old · age verified by ledger binary search
$338K
Outbound · sweep tranches, weeks 1–7
125K
98K
112K
96K
119K
104K
101K
W1
W2
W3
W4
W5
W6
W7
Parking wallet A
Parking wallet B
Both destinations created the same day. Near-static balances between sweeps.
Pull on one thread, and the scale multiplies at every step
Following just the sending side of that wallet, seven more verified hops later, the scale has gone from $338,000 to a node handling 1.07 billion dollars in a single counterparty relationship. Each hop escalates. Each hop was checked directly against the transfer ledger, not assumed.
FIG 3Seven hops, $338K to $1.07B
Logarithmic scale. Bar height is the order of magnitude of volume the node handles, not a linear amount — a linear chart would render the first six hops invisible.
$338K
$1.2M
$4.8M
$12.5M
$47M
$149M
$412M
$1.07B
HOP 0
TVqpWKbBYAJAM3sm3gnAz7i8o111111111
HOP 1
TWtELYC3QETYZ7RheRUo2wZJ17bYtd9ot1
HOP 2
TXaGwr2UBP8U6arFKjC39x53jtpBT3za1r
HOP 3
TCcRVByJeS1RKXPNiqrCHFvNkpkGi4w18L
HOP 4
TAt9HSbvFfAQk6Q1SQFXuuUywcJe2iB9A8
HOP 5
TPRkVYNdBRS4GqF2fcV3frs4PMyFZAUw7M
HOP 6
TPFK7fkPWSb1eedwLhEwyc2DtAUq5VAV3M
HOP 7
TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH
3,165×
total escalation, origin to terminal node
7 / 7
hops checked against the transfer ledger directly
≈3.2×
median step multiplier, no single anomalous jump
The money comes back to where it started
At the top of that climb, the chain does something a random escalation wouldn’t do: it loops. Money leaves one address, passes through three more hops, and roughly 13% of it — $143.9 million — returns to the exact same address it started from. That’s not coincidence at this scale. That’s either one operation moving its own money through intermediaries, or an extremely tight, repeated bilateral relationship between two large entities. Either way, it’s structure, not noise.
FIG 4A four-hop circuit that returns 13% of its own value
$1.07B out · $143.9M returned
TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH
$1.07B
TAt9HSbvFfAQk6Q1SQFXuuUywcJe2iB9A8
hop 1
TPRkVYNdBRS4GqF2fcV3frs4PMyFZAUw7M
hop 2
TPFK7fkPWSb1eedwLhEwyc2DtAUq5VAV3M
hop 3 · loop closes
↑ 13% returns to TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH
What comes back, against what left
Value dispatched through the circuit
$1.07B
Value returning to the origin address
$143.9M
Two readings fit: one operator cycling its own liquidity through intermediaries, or an extremely tight bilateral relationship between two large entities. Both are structure. Neither is noise.
It deliberately sheds the one enforcement tool that exists on this chain
Running in parallel, several of these same addresses convert USDT into USDD through Sun.io’s real, publicly confirmed SmartExchangeRouter contract, verified by finding the actual bot-timed, sub-two-minute relay transactions, not assumed from behaviour alone.
This matters because USDT can be frozen by Tether at law enforcement’s request, and has been. USDD, issued by the TRON DAO, cannot. Converting through this specific contract doesn’t just move value — it strips away the single lever that could otherwise stop it.
FIG 5What the conversion actually buys: freeze immunity
Held as USDT
Freezable
Issuer
Tether Ltd
Blacklist
Yes, on-contract, used repeatedly
Precedent
Billions frozen at LE request
→
Held as USDD
Not freezable
Issuer
TRON DAO
Blacklist
No equivalent mechanism
Route
Sun.io SmartExchangeRouter
< 2 min
median relay time between receipt and conversion, bot-timed
Confirmed
router contract verified from actual transactions, not inferred
Parallel
runs alongside the escalation chain, not downstream of it
Four ghosts keep reappearing
Across branches reached completely independently of each other, the same unlabeled addresses keep showing up: as a sender here, a bidirectional partner there, a funder somewhere else. One address, TZ29k1iPA8TNLTW43bc6sDDXZbcGHSbpik, is simultaneously a $12.5 million USDT recipient, the confirmed funder of a separate node in the USDD network, and a receiver from three different upstream sources. That’s not adjacency. That’s the same small set of hands touching multiple parts of the machine.
FIG 6Four unlabeled anchors, and the roles each one plays
Reached via independent branches
TS4Y9AeZ5tNoL6bRR9PqC6KPPVwr2wxB4i
4 branches
Recurring funder across four independently-reached recipients. No label in any database.
TDutyPwkEwHogyt1kJPYQQk3gP66S6U4h8
4 branches
Simultaneously a direct recipient of the origin wallet and an anchor for three others.
TZ29k1iPA8TNLTW43bc6sDDXZbcGHSbpik
3 branches
$12.5M USDT recipient, confirmed funder of a separate USDD-network node, receiver from three upstreams.
TKU7jnAvN12tCLV4MqaktQdrztv9WqQfgU
3 branches
Largest single relationship for TYhNWA1VLK at $90,447; bidirectional with two further branches.
Bars scaled to the number of independently-reached branches each address appears in. None carries an exchange or entity label in any database we queried.
Nobody official has this on their radar
We checked the entire chain, every major node, against two independent professional compliance databases: Bitquery and BlockSec/MetaSleuth. Every single major exchange wallet we’ve encountered anywhere else in this investigation got tagged instantly by at least one of them. Here: nothing. Not the billion-dollar node, TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH. Not the $149 million relationship. Not one of them. At this scale, that absence is itself the finding.
FIG 7Coverage check: every major node, two databases, zero hits
Control group: the labeled exchange wallets encountered elsewhere in this investigation, all of which tagged instantly.
Nodes in this network
TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH
$1.07B terminal
no hit
no hit
TPFK7fkPWSb1eedwLhEwyc2DtAUq5VAV3M
$412M relay
no hit
no hit
TPRkVYNdBRS4GqF2fcV3frs4PMyFZAUw7M
$149M loop origin
no hit
no hit
TAt9HSbvFfAQk6Q1SQFXuuUywcJe2iB9A8
$47M aggregator
no hit
no hit
TCcRVByJeS1RKXPNiqrCHFvNkpkGi4w18L
$12.5M USDD funder
no hit
no hit
TVqpWKbBYAJAM3sm3gnAz7i8o111111111
vanity collector
no hit
no hit
Bitquery
MetaSleuth
Hit rate, this network vs. control
Known exchange wallets (control)
100%
Tagged instantly by at least one database
Every major node in this chain
0%
Including the $1.07B node and the $149M relationship
Either this is a genuinely enormous, entirely undocumented financial operation, or it is something large and private enough that mainstream compliance tooling simply hasn’t caught up to it.
What we’re confident about, and what we’re not
Established
The origin is a documented black-market directory's own payment wallet, not a hunch or a tip.
The mesh at the origin is provably dense: eight of nine direct recipients tie back to the same six anchors, verified across independent paths.
The seven-hop escalation to a $1.07B counterparty relationship was checked hop by hop against the transfer ledger.
The USDT→USDD conversions run through Sun.io's real SmartExchangeRouter, confirmed from actual sub-two-minute relay transactions.
Not asserted
Who controls this network. We are naming no operator.
Whether it is one operator or several entities in genuine business with each other.
What specifically funds the bottom of it. The dust-level inbound has no attributable source.
Whether TALsXrymdL belongs to this network at all. Its overlap is unresolved and it is excluded from the mesh count.
Why this is worth publishing
Because it starts at a documented black-market directory, not a hunch. Because the structuring, the parking wallets, the circular flow, and the deliberate freeze-evasion aren’t individually damning, but together they form a coherent, deliberate shape. Because the mesh at the origin is provably dense, not a single coincidental path we got lucky following.
And because nothing here is on the map of the two most-used compliance tools in the industry, which means either we’ve found something nobody else has, or we’ve found the edge of what on-chain tooling alone can actually see. The piece is “here is a real, verified, unlabeled network moving at exchange scale, discovered by following a black-market search bot’s own payment wallet” — not a claim about who’s behind it.
We’ll keep watching this one too.
APPENDIXEvery address referenced in this piece, in full
23 addresses · all checksums verify clean
Origin
TBRdQCfUu33bSJziHWoj9QArxV82KVt4E5
The 超搜 rotating deposit wallet this whole trail started from
The escalation chain, in order
TVqpWKbBYAJAM3sm3gnAz7i8o111111111
Vanity collector, ~7 weeks old, 2,187 senders
TWtELYC3QETYZ7RheRUo2wZJ17bYtd9ot1
Sweep target
TXaGwr2UBP8U6arFKjC39x53jtpBT3za1r
Relay
TCcRVByJeS1RKXPNiqrCHFvNkpkGi4w18L
USDD-network funder, $12.5M USDT recipient
The four loop nodes
TNo9eGDGMY8g9XGH7kNAMQePE5ut2YRWUH
The hub · $1.07B single counterparty relationship
TAt9HSbvFfAQk6Q1SQFXuuUywcJe2iB9A8
Loop hop 1
TPRkVYNdBRS4GqF2fcV3frs4PMyFZAUw7M
Loop hop 2 · $149M relationship
TPFK7fkPWSb1eedwLhEwyc2DtAUq5VAV3M
Loop hop 3 · where $143.9M closes back to the hub
Direct recipients of the origin wallet, checked in the mesh
TMw4hJrYrHDYSJXEwVVrgbvuhgHZGHiAAQ
100% of outbound to OKX · $204,655 / 30 txns
TYhNWA1VLKPT7w9JMcSTxX2sW4zfbK9NsU
$524,496 / 76 txns · 6 of 6 anchor ties
TDutyPwkEwHogyt1kJPYQQk3gP66S6U4h8
Both a recipient and an anchor for three others
TPs3xXe6z28KzMKu2QrTvLq2CN7ztHRZMV
100% outbound to a single address
TA89c9d2dMtc1vnzS3hhrMZVTqoS7ChHVm
Touches Binance-Hot 10 · $10,000
TAEsmyvam88kU7v7nwoiarnG73vJmveaTs
One anchor tie
TQUqCq1og9YKVa3DmbrxBY5YPLzi14trqj
One anchor tie
TALsXrymdLKpXYXzPDoeLddm8JPjLmygrk
Unresolved outlier · 6,807 transfers, no anchor overlap, excluded from the mesh count
Recurring unlabeled anchors
TS4Y9AeZ5tNoL6bRR9PqC6KPPVwr2wxB4i
Funder across four independently-reached recipients
TDutyPwkEwHogyt1kJPYQQk3gP66S6U4h8
Also listed above as a direct recipient
TZ29k1iPA8TNLTW43bc6sDDXZbcGHSbpik
$12.5M recipient, USDD-node funder, three upstreams
TKU7jnAvN12tCLV4MqaktQdrztv9WqQfgU
Largest single relationship for TYhNWA1VLK, $90,447
TLxZm8HJKBzLfiqs15pBL27M12PbpsmkG3
Recurring across two independent branches
Confirmed exchange wallets — routine infrastructure, not part of the network’s own structure
TLaGjwhvA8XQYSxFAcAXy7Dvuue9eGYitv
OKX hot wallet · touched by 5 of 9 recipients
TCLgK89AnXbC9rewvhNb9UgXCc2qJJpBXh
Binance-Hot 10
Addresses are listed for verification against public block explorers. Inclusion in this register is not an assertion of wrongdoing by any address holder; the exchange hot wallets in particular are ordinary infrastructure touched by very large numbers of unrelated parties.