View source for RANT Token Flawed Contract Sell Burn Liquidity Pair Logic

{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/ranttokenflawedcontractsellburnliquiditypairlogic.php}}
{{Unattributed Sources}}

[[File:Binancesecurity.jpg|thumb|Generic Binance Security Image]]The RANT token, launched on July 3rd without any identifiable team, website, or social media presence, suffered a major exploit just two days later due to flawed smart contract logic. A vulnerability in the _sellBurnliquidityPairTokens function allowed attackers to manipulate token prices by triggering disproportionate burns through small transfers, ultimately distorting liquidity pool reserves. This exploit led to a loss of approximately $203.8K, with the attacker swapping stolen BNB for USDC and bridging it out via the Across Protocol. Security firms like TenArmor and SlowMist flagged the suspicious activity, but the project's anonymous nature and lack of oversight make recovery unlikely, with further details still potentially forthcoming.<ref name="slowmisttweet-20520" /><ref name="agentlistaitweet-20521" /><ref name="agentlisa2-20522" /><ref name="ranttokenaddressbscscan-20523" /><ref name="exploittransaction-20524" /><ref name="tenarmortweet-20525" /><ref name="bscscanexploiter-20526" /><ref name="ranttokencreationtransaction-20527" />

== About RANT Token ==
The RANT Token was originally launched on July 3rd. No sources have been able to tie this token to a social media, website, or other identifier.

== The Reality ==
The RANT Token smart contract appears to have been launched with flawed smart contract logic.

== What Happened ==
The RANT token on BNB Chain was exploited just two days after launch due to flawed burn logic in its smart contract, allowing an attacker to manipulate prices and steal approximately $204,000.
{| class="wikitable"
|+Key Event Timeline - RANT Token Flawed Contract Sell Burn Liquidity Pair Logic
!Date
!Event
!Description
|-
|July 3rd, 2025 5:47:40 AM MDT
|RANT Token Contract Created
|The RANT Token smart contract is first launched on the Binance Smart Chain.
|-
|July 5th, 2025 9:16:36 AM MDT
|Time Of Exploit Transaction
|The exploit transaction on the Binance Smart Chain.
|-
|July 5th, 2025 9:28:00 AM MDT
|TenArmor Alert Tweet Posted
|TenArmor posts a tweet alerting to the suspicious transaction.
|-
|July 5th, 2025 9:59:00 AM MDT
|SlowMist Posts Detection Notice
|SlowMist posts a notice about suspicious activity associated with the RANT token.
|-
|July 7th, 2025 3:50:00 AM MDT
|MetaTrust Alert Tweet
|MetaTrust posts an alert tweet with details about the exploit, which they appear to have generated through their Agent Lisa program.
|-
|July 7th, 2025 4:04:00 AM MDT
|Agent Lisa Report Exploit
|An entity referred to as "Agent Lisa" posts a more detailed explanation of the vulnerability, which it claims was detected within minutes.
|}

== Technical Details ==
On July 5, a vulnerability was exploited in the #RANT token on the #BNBChain, resulting in a loss of approximately $204,000. The token had only been live for three days before the incident occurred. The root of the attack lay in the flawed token burn logic, specifically in how the smart contract handled burn operations during token sales. The mechanism allowed attackers to manipulate token prices by exploiting a weakness in how burn amounts were calculated.

The key issue was found in the _sellBurnliquidityPairTokens function, which mistakenly based the burn amount on the user’s transfer amount instead of referencing the liquidity pair’s actual balance. This oversight enabled attackers to perform small token transfers that triggered disproportionate burns from the liquidity pool, distorting the reserve ratios and inflating the token price. This type of manipulation opened the door for the attacker to profit by selling tokens at artificially high prices.

To execute the exploit, the attacker manipulated the price through this flawed logic, stole BNB, then swapped the funds for USDC. Finally, the stolen assets were bridged out using the Across Protocol. The incident highlights the critical need for more secure smart contract logic. Experts recommend adjusting the burn calculation to rely on the liquidity pool’s balance or using a fixed percentage to ensure fairness and prevent such exploits through small-scale manipulations.

Attacker: 0xad2cb8f48e74065a0b884af9c5a4ecbba101be23

== Total Amount Lost ==
The loss amount was reported as $203.8k by TenArmor.

The total amount lost has been estimated at $204,000 USD.

== Immediate Reactions ==
SlowMist reported detecting "potential suspicious activities". "MistEye has detected potential suspicious activities related to $RANT on BSC."

== Ultimate Outcome ==
It is unclear who is behind the RANT token project and whether any outcome was achieved.

== Total Amount Recovered ==
There is no evidence of any recovery being possible.

There do not appear to have been any funds recovered in this case.

== Ongoing Developments ==
The incident happened recently and further details may emerge over time.
== Individual Prevention Policies ==
{{Prevention:Individuals:Placeholder}}

{{Prevention:Individuals:End}}

== Platform Prevention Policies ==
{{Prevention:Platforms:Placeholder}}

{{Prevention:Platforms:End}}

== Regulatory Prevention Policies ==
{{Prevention:Regulators:Placeholder}}

{{Prevention:Regulators:End}}

== References ==
<references><ref name="slowmisttweet-20520">[https://twitter.com/SlowMist_Team/status/1941527248533881113 SlowMist - "MistEye has detected potential suspicious activities related to $RANT on BSC." - Twitter/X] (Accessed Jul 8, 2025)</ref>

<ref name="agentlistaitweet-20521">[https://twitter.com/AgentLISA_ai/status/1942162776379797641 Agent Lisa - "The #RANT token on #BNBChain was exploited via a critical logic vulnerability in its _sellBurnLiquidityPairTokens function: Attackers used user transfer amounts instead of liquidity pair balances to manipulate token burning, draining $204K in funds." - Twitter/X] (Accessed Jul 8, 2025)</ref>

<ref name="agentlisa2-20522">[https://agentlisa.ai/scan/b0d8e7cd-a163-4c70-9e3d-372513a1041d RANTToken Attack - Agent Lisa] (Accessed Jul 8, 2025)</ref>

<ref name="ranttokenaddressbscscan-20523">[https://bscscan.com/address/0xc321ac21a07b3d593b269acdace69c3762ca2dd0 Address Referenced By SlowMist - BSCScan] (Accessed Jul 8, 2025)</ref>

<ref name="exploittransaction-20524">[https://bscscan.com/tx/0x2d9c1a00cf3d2fda268d0d11794ad2956774b156355e16441d6edb9a448e5a99 Exploit Transaction - BSCScan] (Accessed Jul 8, 2025)</ref>

<ref name="tenarmortweet-20525">[https://twitter.com/TenArmorAlert/status/1941519470016557290 TenArmor - "Our system has detected a suspicious attack involving #RANT on #BSC, resulting in an approximately loss of $203.8K." - Twitter/X] (Accessed Jul 8, 2025)</ref>

<ref name="bscscanexploiter-20526">[https://bscscan.com/address/0xad2cb8f48e74065a0b884af9c5a4ecbba101be23 Exploiter Address - BSCScan] (Accessed Jul 8, 2025)</ref>

<ref name="ranttokencreationtransaction-20527">[https://bscscan.com/tx/0xc13be0a13ce6a51a575512d1fb6ee0ff87d6987965e728b4c31e2c3a6009fb15 Rant Token Creation Transaction - BSCScan] (Accessed Jul 8, 2025)</ref></references>