A fresh USDC blacklist action froze nearly $100,000 on Ethereum early Friday, while a separate daily monitoring report flagged 14 transfers worth roughly $78,900 that were sent to wallets already recorded as blacklisted.
USDT/USDC Ban List recorded Ethereum address 0xe07bd590e1198666230932bad5db3dbbe21e7d57 being added to the USDC blacklist at 05:00:59 UTC on September 25. The address held 99,989.91 USDC at the time according to the tracker.
The blacklist event itself can be independently corroborated through issuer-contract monitoring. A separate blockchain tracker that reads freeze and blacklist events directly from stablecoin contracts recorded the same Ethereum address being blacklisted for USDC at approximately 05:00 UTC, linked to transaction 0xa112187d419a9eae5c6ef89defb40227f10793467cd470447be9b1d2a2ac4fb2.
What remains unknown is why the address was targeted. There is currently no public evidence connecting the freeze to a hack, fraud investigation, sanctions case, law-enforcement request or any specific illicit activity. The blockchain establishes that the address was blacklisted; it does not establish the reason.
The Fresh $99,989 Freeze Is Separate From the Daily $2.8 Million Tally
The roughly $100,000 Ethereum freeze also needs to be separated from the tracker’s September 25 daily report, which covers an earlier reporting window.
That report recorded 27 new blacklist actions involving approximately $2.8 million in stablecoins. Three were Ethereum addresses holding a combined roughly $355,500, while another 24 were Tron addresses holding about $2.5 million. The report also recorded one address being removed from a blacklist.
The three Ethereum actions included two USDT balances of approximately $159,156 and $150,025 and one USDC balance of roughly $46,321. On Tron, the largest single reported freeze was close to $600,000 in USDT.
The new 99,989.91-USDC event occurred at 05:00 UTC on September 25 and therefore should not simply be added to the 27 addresses as though it were one of the same reported actions.
The latest activity follows other large stablecoin blacklist events tracked this month. DaveFinances recently reported on a wave of stablecoin blacklists that froze about $3.4 million, highlighting how frequently issuer-controlled freeze mechanisms now appear in routine on-chain monitoring.
Tracker Says 14 Payments Reached Already-Blacklisted Wallets
The more unusual part of Friday’s report was not the size of the new freezes but what allegedly happened after other addresses had already been blacklisted.
USDT/USDC Ban List said it detected 14 transfers totaling approximately $78,900 to wallets that were already on stablecoin blacklists. The tracker characterized those funds as effectively lost because the destinations had already been restricted.
The available public report does not provide enough transaction-level attribution to reliably identify all 14 senders, however. There is therefore no basis at this stage to say that a particular exchange, payment processor, broker or other financial platform was responsible for the transfers.
Nor does a transfer to a blacklisted destination by itself establish misconduct by the sender. Depending on the token, chain and contract implementation involved, the operational consequences of blacklisting can differ, and individual transactions require separate examination before conclusions can be drawn about who initiated them and what screening was in place.
Still, the activity is worth investigating because the blacklist status existed before the payments were recorded. If any of the senders ultimately turn out to be regulated exchanges, centralized payment services or automated payout systems, the timing would raise questions about whether their transaction-screening systems were checking destination addresses against current stablecoin restrictions before releasing funds.
Circle Can Freeze USDC, but the Contract Event Does Not Explain Why
USDC is different from cryptocurrencies such as Bitcoin because its issuer retains administrative capabilities over the token contract.
Circle’s USDC terms state that the company can block certain addresses and freeze associated USDC under its blocklisting policy. The terms also contemplate situations involving suspected illegal activity, violations of its rules and valid government legal orders.
None of those general provisions should be treated as an explanation for Friday’s $99,989.91 freeze. Circle has not publicly identified the owner of the address or disclosed a specific reason for the blacklist action.
That distinction is important because stablecoin freezes sometimes do come with explicit attribution. For example, DaveFinances previously covered Tether, TRON and TRM Labs freezing hundreds of millions of dollars linked to illicit activity, where the parties involved publicly described the enforcement rationale. No comparable explanation has surfaced for the newly blacklisted USDC wallet.
The 14 Post-Blacklist Payments May Be the More Important Signal
From an investor and payments-industry perspective, a $99,989 freeze is relatively small compared with the hundreds of millions of dollars that stablecoin issuers have immobilized in major enforcement actions. The 14 payments to already-blacklisted wallets may reveal a more interesting operational problem.
Blacklist data is generated on-chain. Once an issuer executes a blacklist transaction, that status can be detected programmatically. A platform processing stablecoin payments therefore does not necessarily need to wait for a sanctions bulletin, press release or manually updated spreadsheet before recognizing that a destination has become restricted.
If a centralized service continues paying such an address after the on-chain event, several explanations are possible. Its screening database could be stale. Its address checks might run only during customer onboarding rather than immediately before withdrawals. An automated payout system might not consume issuer-contract events in real time. Or the sender could simply be an individual wallet with no screening process at all.
At present, there is not enough evidence to determine which explanation applies to the 14 transfers reported Friday. That is why identifying the senders matters.
Real-Time Blacklist Screening Is Becoming an Operational Issue
The episode illustrates a broader challenge created by centralized stablecoins. The ability to freeze tokens can help issuers respond to hacks, fraud and enforcement requests, but it also creates a continuously changing layer of counterparty risk for businesses moving USDT and USDC.
A destination considered usable at one moment can become restricted later. Screening an address once is therefore not necessarily enough for a platform processing thousands of withdrawals or merchant settlements each day.
This is especially relevant on Tron, which accounted for 24 of the 27 new bans in the tracker’s daily report. Previous episodes have likewise involved sizable concentrations of frozen USDT on the network, including 15 Tron wallets holding about $3.3 million in USDT.
For exchanges and payment companies, the practical response is likely to be increasingly close to transaction time: checking the destination against issuer blacklist events immediately before a transfer is released rather than relying entirely on periodic compliance-list updates.
There is also an opportunity for blockchain analytics and compliance providers capable of converting contract events into low-latency alerts that can be integrated directly into withdrawal and payment systems.
But Friday’s figures should not be pushed further than the evidence allows. The roughly $100,000 USDC wallet is confirmed as blacklisted, but its owner and the reason remain unidentified. The tracker reports 14 post-blacklist transfers worth around $78,900, but their senders have not been reliably attributed in public data.
If those addresses can be traced to identifiable services, the story changes from an unusual on-chain observation into a measurable test of how quickly crypto businesses react when stablecoin issuers blacklist a destination. Until then, the transactions are a warning signal rather than proof of a compliance failure.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.