Tikkala Security

367 posts

Tikkala Security

Tikkala Security

@TikkalaResearch

Securing Web2 & Web3, auditing and penetration testing.

Menlo Park, CA Katılım Kasım 2024
3 Takip Edilen665 Takipçiler
Tikkala Security
Tikkala Security@TikkalaResearch·
Root cause is ............. re-entry. The most famous and popular one still. The sell() function does not clear the user's balance.
Tikkala Security tweet media
English
1
0
2
1.5K
Tikkala Security
Tikkala Security@TikkalaResearch·
The unknown function selector 0x83c7b8e4 allows transferFrom of any user who previously approved the $ETF token (bscscan.com/address/0xec7b…) and swap with $USDT. In that transaction, 22 victims' $ETF tokens were attacked.
English
0
0
1
2.8K
Tikkala Security
Tikkala Security@TikkalaResearch·
@doom_cats 2/ The attacker created 60 contracts and kept calling rescue() to force the victim contract to swap out more Heaven Gate ($HATE Token) while putting 5 WETH into the swap. This affects the K value, allowing the attacker to profit using a sandwich attack.
Tikkala Security tweet media
English
1
0
2
1.7K
Tikkala Security
Tikkala Security@TikkalaResearch·
@EdenNetwork The locker account could be any one, the startTime is from user input, the lock receiver could be any one, too.
Tikkala Security tweet media
English
0
0
2
759
Tikkala Security
Tikkala Security@TikkalaResearch·
In the function collectInterestRepayment(), it allows transferFrom from any account that had allowance, and the sharePrice will be updated. An attacker could stake some tokens and then withdraw more after the price is inflated.
Tikkala Security tweet mediaTikkala Security tweet media
English
1
0
2
787