EthSecurity
5.22K subscribers
112 photos
20 files
763 links
Download Telegram
vow protocol hacked for $1.2 m. seems admin private key has leaked and hacker changed usdRate to mint $vusd. @EthSecurity1
🔥4😢4😱2🍾1
a victim was drained for 55.4M DAI

Transaction hash
0xf70042bf3ae7c22f0680f8afa078c38989ed475dfbe5c8d8f30a50d4d2f45dc4

Theft address
0x5D4b2A02c59197eB2cAe95A6Df9fE27af60459d4 @EthSecurity1
If I want to consider bad situation, maybe telegram team decide to erase databases
Please follow my x account

https://x.com/ethsecurity
@EthSecurity1
71
A periphery contract of AAVE is hacked due to an arbitrary call/logic error.
Loss ~ $30k
@EthSecurity1
3🔥2
Pythia staking contract was drained in suspicious claimRewards() calls by
eth:0xd861e6F1760d014D6EE6428cF7F7d732563c74c0
The profit was swapped for 21 ETH (~$53K) and has been deposited to Tornado Cash. @ethsecurity1
👍2
The $27M Penpiexyz exploit @EthSecurity1
🔥5
Forwarded from zilayo
Rough overview ignoring the flashloan stuff. Have barely looked at penpie/pendle contracts previously so a lot of context is missing.

Step 1:
> create YT/PT yield contract where the underlying asset is attacker controlled contract
> Create new pendle market with the PT
> Mint a bunch of PT - PT uses the underlying (attacker contract) for balance/exchange rate logic
> Mint a bunch of YT
> Transfer PT to pendle market
> Mint LP via the pendle market. Again, uses the attacker contract for rewards logic.
> Deposit LP into penpie

Step 2:
> Batch harvest penpie rewards. This uses the attacker's contract for reward logic.
> Penpie calls claimRewards on the attacker contract which hands over control mid execution
> During the re-entrancy, attacker contract adds a bunch of single sided pendle liquidity using legit PT tokens + deposits LPs into penpie
> Penpie grants approval on a bunch of legit LP tokens to a second attacker contract and then calls this attacker contract to queueNewRewards. During the reentrancy, the attacker transfers previously approved LPs from the penpie staking contract -> attacker contract 2.
> Attacker then calls MasterPenie to multiclaim rewards. Again this uses the attacker's second contract for reward logic and hands over control mid execution. Attacker transfers LPs from contract 2 -> contract 1 during this step.
> Attacker withdraws legit LPs from penpie and removes single sided pendle liquidity for them. At this stage, they receive more of the underlying than was originally used to create the LPs.
🆒4
Solidity signature verification checklist : - Check if the returned public key matches expected public key.
- Check if the Signature has not already been used (use nonce) - Check if the signature is intended for the specific blockchain you are executing the smart contract on. This can be checked using the chainId (Relevant only for contracts deployed on multiple EVM chains) - Check if the Signature is used from the right person (if not everyone should be able to use it)
- Check if the deadline is not expired (if it is not needed that the signature is working forever)
Here is a good article that teaches about signatures: https://medium.com/coinmonks/ethereum-signatures-for-hackers-and-auditors-101-4da766cd6344 @EthSecurity1
🔥62👏1
- On September 4th, 2024, (CUT token) was exploited and lost ~$1.4 million.

To learn more about the incident, read full analysis here 👇 https://www.certik.com/resources/blog/caterpillar-coin-cut-token-incident-analysis
- On September 11th, 2024,
The exploiter transferred various asset tokens (~$20M) from several hot indodax wallet addresses.

eth/pol: 0x3C02290922a3618A4646E3BbCa65853eA45FE7C6
tron: TWe5pEnPDetzxgJS4uN26VFg15wWtdcTXc
btc: 1JUToCyRL5UwgeucjnFAagKs4v1YqhjT1d

@EthSecurity1
👍2
The L2 DAI deployer for DAI vanity addresses has been compromised, as it was generated by the vulnerable Profanity tool. All networks other than Optimism and Arbitrum are at risk, as the attacker can create honeypots with the same address. - 𝕏/@godsflaw
Delta Prime @DeltaPrimeDefi admin private key leaked. All pools are drained. $11M loss already. Withdraw ASAP!

Details of the hack:

A hacker gained control of 0xx40e4ff9e018462ce71fa34abdfa27b8c5e2b1afb, which is the admin of proxies. Then, the hacker upgraded the proxies to point to malicious contract 0xD4CA224a176A59ed1a346FA86C3e921e01659E73.

This malicious contract can inflate the deposited amount of the hacker on all pools.
@EthSecurity1
🔥6
We passed 4000 subscribers
Thanks mates
🔥14