YULI AI Token Contract Pool Spot Price Manipulation Exploit
Notice: This page is a freshly imported case study from an original repository. While the original content had a similar format, some sections may not have been fully completed. Please help fill in any empty sections or any missing information you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!
The YULI AI smart contract, launched on July 22, 2025, was exploited due to a vulnerability that allowed a price manipulation attack. According to TenArmor, the attacker manipulated the YULIAI/USDT V3 pool’s spot price to repeatedly sell YULIAI tokens and extract more USDT from the contract, resulting in an estimated loss of $78.8K. The identity of the project’s creators remains unknown, and it is unclear whether an investigation is ongoing or if affected users will receive any support.[1][2][3][4][5][6]
About YULI AI
The YULI AI smart contract was first created on July 22nd, 2025.
The Reality
Unfortunately, the smart contract was vulnerable to a price manipulation attack.
What Happened
The YULI AI smart contract on Binance Smart Chain was exploited through a price manipulation attack causing a $78.8K loss.
| Date | Event | Description |
|---|---|---|
| July 22nd, 2025 3:25:26 AM MDT | YULI AI Smart Contract Created | The YULI AI smart contract is initially created on BSC. |
| August 5th, 2025 8:20:04 PM MDT | Initial Attack Wallet Funding | The attacker's wallet is initially funded. |
| August 13th, 2025 2:02:17 AM MDT | Attack Transaction Occurred | The attack transaction is accepted by the Binance smart chain. |
| August 13th, 2025 8:24:00 PM MDT | TenArmor Posts Attack Alert | TenArmor made a post on Twitter/X about the attack. |
Technical Details
TenArmor provided the following analysis: "It appears to be a price manipulation attack, where the contract 0x8262 relies on the YULIAI/USDT V3 pool's spot price for selling YULIAI tokens. After manipulating the pool's YULIAI price, the attacker obtained more USDT from the victim contract by repeated selling YULIAI tokens."
Total Amount Lost
TenArmor reports that there was "an approximately loss of $78.8K".
The total amount lost has been estimated at $79,000 USD.
Immediate Reactions
The incident was reported on by TenArmor.
Ultimate Outcome
It is unclear whether any resolution will be possible.
Total Amount Recovered
There are no public details about who is behind this project.
There do not appear to have been any funds recovered in this case.
Ongoing Developments
It is unclear if an investigation is underway or any assistance will be available for affected users.
Individual Prevention Policies
No specific policies for individual prevention have yet been identified in this case.
For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.
Platform Prevention Policies
Policies for platforms to take to prevent this situation have not yet been selected in this case.
For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.
Regulatory Prevention Policies
No specific regulatory policies have yet been identified in this case.
For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.
References
- ↑ TenArmor - "Our system has detected that #YULIAI and an unverified contract 0x8262 on #BSC was attacked, resulting in an approximately loss of $78.8K." - Twitter/X (Accessed Sep 23, 2025)
- ↑ Attack Transaction - BSCScan (Accessed Sep 23, 2025)
- ↑ Exploiter Address - BSCScan (Accessed Sep 23, 2025)
- ↑ Exploiter Address Funding - BSCScan (Accessed Sep 23, 2025)
- ↑ YULI AI Token - BSCScan (Accessed Sep 23, 2025)
- ↑ YULI AI Token Creation - BSCScan (Accessed Sep 23, 2025)