TENDRIL/USDT pool on BSC attacked, with losses of approximat
On November 5, 2026, TenArmorAlert detected what appeared to be an attack on the TENDRIL/USDT pool on BSC, with losses of approximately $309,000. PANews and Odaily both reported on the incident in succession, with consistent core facts, but the attack method, fund flows, and the project team's response were not disclosed.
Event Timeline
- [11-05 07:05] The TENDRIL/USDT pool on BSC was attacked, with losses of approximately $309,000 (PANews)
- [11-05 07:06] The TENDRIL/USDT pool on BSC was suspected of being attacked, with losses of approximately $309,000 (Odaily)
Background and Impact
On November 5, 2026, the on-chain security monitoring account TenArmorAlert posted on X that its system had detected a suspicious attack involving the TENDRIL/USDT pool on BSC, causing losses of approximately $309,000. PANews reported at 07:05 that day under the headline "TENDRIL/USDT Pool on BSC Attacked, Losses of Approximately $309,000," and Odaily followed up at 07:06 with "TENDRIL/USDT Pool on BSC Suspected of Being Attacked, Losses of Approximately $309,000." The core information in both reports is consistent: the network involved was BSC, the trading pair involved was TENDRIL/USDT, the scale of losses was approximately $309,000, and the source of the information was TenArmorAlert's monitoring disclosure.
In terms of wording, there is a subtle difference between the two outlets in how they characterize the incident. PANews used "attacked" directly in its headline, but its body text, like Odaily's, described it as a "suspicious attack" or "suspected of being attacked"; neither characterized the incident as a confirmed attack. Apart from the loss amount, neither report disclosed the attack method, the attacker's address, or the specific flow of funds, nor did they state whether the relevant liquidity pool had been paused or whether the project team had responded or taken remedial measures. In other words, the available information remains at the stage of a unilateral disclosure by the monitoring firm, and the nature of the incident and the full scope of losses still await verification from more information.
As for the scope of impact, the available materials point only to a single TENDRIL/USDT pool on BSC and do not mention whether other trading pairs, protocols, or cross-chain assets beyond that pool were affected. For liquidity providers, a pool-level attack typically corresponds directly to an imbalance in the ratio of assets in the pool and changes in the net value of shares, but this report did not provide the pool's size, TVL, or the specific path by which funds were withdrawn, so it is impossible to assess how the losses were actually distributed among participants. At approximately $309,000, this is a relatively limited individual case within the entire BSC ecosystem, and its market spillover effects remain to be seen.
It should be noted that this disclosure involves only an on-chain pool on BSC; it does not mention any centralized trading platform, nor does it explain TENDRIL's project background or exchange listings. When readers look up entry information such as Huobi HTX registration APP download, Zhima Gate.io registration APP download, Bitget registration APP download, Binance registration APP download, and OKX registration APP download, they should distinguish such download and registration needs from this incident; there is no connection between the two in the materials. Until the project team or additional monitoring firms provide further explanation, the incident timeline still consists only of the "monitoring alert—media relay" link.
Frequently Asked Questions
### How large were the losses in this attack, and who will be affected?
According to TenArmorAlert's monitoring, the losses were approximately $309,000. The available materials point only to the TENDRIL/USDT pool on BSC and do not mention other trading pairs, protocols, or cross-chain assets being affected; the direct impact is mainly on participants in that pool.
### Is there any chance the funds can be recovered, and what milestones should we watch going forward?
Neither report mentioned fund recovery, freezing, or the attacker's address. Going forward, it is worth watching whether TenArmorAlert publishes an analysis of fund flows, whether the TENDRIL project team responds publicly, and whether the relevant pool is paused.
### Does a stablecoin trading pair mean there is no risk?
Although TENDRIL/USDT is denominated in USDT, the risk comes from the pool itself rather than the denominating asset. In this incident, it was precisely this pool that was affected, showing that having a stablecoin in a trading pair does not mean the funds are safe; attention still needs to be paid to the pool contract and changes in liquidity.