EthSecurity
5.22K subscribers
112 photos
20 files
759 links
Download Telegram
⚑1
what is domain separator?
                                                                   The domain separator helps prevent signature reuse attacks in DeFi protocols by making signatures unique to a particular contract and message type. Here are some more details:                                                          

Without a domain separator, a signature could potentially be reused for different messages or contracts. This enables various attacks.

For example, a signature approving a small transfer amount could be reused to approve a large transfer on another contract.Or a signature meant for a benign callback could be reused to trigger funds transfers.

The domain separator binds a signature to a specific contract address and message type.

It is computed from the contract address, a salt value, and the message EIP-712 typehash.When generating a signature, the signer computes and includes the domain separator.When verifying a signature, the contract recomputes the expected domain separator.If the domain separators don't match, the signature is invalid for that context.

This prevents simply replaying a signature on another contract/message type.

Even a tiny change to the contract address, salt, or message typehash invalidates old signatures.

So attackers cannot trivially transfer or forge signatures between contexts.
                                                                                                                               
some potential pitfalls: 
            
Forgetting to specify the domain separator when verifying signatures. This would allow cross-contract/message replay attacks.

Using a constant/hardcoded domain separator value rather than computing it dynamically. This defeats the purpose of making it context-specific.

Not updating the salt value periodically. Over time, old signatures could potentially be replayed on contracts with the same address.

Computing the domain separator incorrectly, such as omitting important components like the contract address. This could again allow reuse across contexts.

Failing to sanitize or validate input values used in domain separator computation. These should not be attacker-controlled.

Setting domain separators on a per-function rather than per-contract basis. This doesn't fully isolate signatures to a single context.

Not accounting for potential metadata like chain/network ID in domain separators. Signatures may not be cross-chain compatible.

Not versioning the domain separator format or hashing algorithm over time. Old styles could be replayed.

Failing to specify expected calldata/function signature when relevant. Signatures for calls are less isolated.

Not regenerating domain separators when upgrading a contract implementation. Old contexts may be accessible.
‍
Insufficient entropy or non-randomness in salt values, compromising uniqueness over time.@EthSecurity1
πŸ‘6❀3
New year start with new loss. Orbit Bridge ~81.5 m $
Happy new year
⚑8πŸ”₯5😒2😁1
😁8πŸ‘2🀯2
2023 web3security Facts:

83% of protocols hacked in 2023 was audited

56.7% rugpulls happened in BSC

Certik-Peckshield-slowmist- Quantstamp are firms that performed security audits on exploited projects(before exploit).

62% projects compensated after exploit

34% projects audited after the exploits

78% attackers accepted bug bounty

@EthSecurity1
πŸ‘9πŸ”₯4⚑1😁1
Easy transferfrom(victim,Hacker,3.3 m $)
Bungee Exploit
@EthSecurity1
πŸ”₯2πŸ‘1
Forwarded from Investigations by ZachXBT
It appears a Ripple insider was hacked for ~213M XRP ($112.5M)

Source address
rJNLz3A1qPKfWCtJLPhmMZAfBkutC2Qojm

So far the stolen funds have been laundered through MEXC, Gate, Binance, Kraken, OKX, HTX, HitBTC, etc

Update: Confirmation of the hack from Chris Larsen (Ripple Co-Founder & Executive Chairman)

Theft addresses
rGhR13XyM43WdDaSMznHd5rZ4cJatybvEg
rHQVKntyfkDCPhEBL2ctryuEAkDZgckmmV
rLsUemhuBZtF44rqqzneb2F9JgyrRYYd4t
rKPERax7t9iFvT3RHXn5nifyNpzp9a4hBa
rpjs4HLX1gJoEenH69PsQmXaXY22QhCYAT
rLRhugR4ysNa2xkt4E6fKN8krs9jatCp6w
rnCyeUNvfDbtTagGEPjBfTCBz6EqJjf2Uj
rHVjfYzTaB8MzSoQGqpzH9barZr85QsZW7
😁3🀯2
Forwarded from Crypto Goodreads
Vitalik wrote about risks of restaking in this article from May 2023.

Good to take a step back sometimes and look at the safety too

πŸ‘‡

https://vitalik.eth.limo/general/2023/05/21/dont_overload.html
Warpcast is strange! Get approves account keys onchain and store eth keys on it's server :(
Eth keys : hold asset(EOA)

@Ethsecurity1
😁10🀬2
- PlayDapp Heist: Attackers minted 200M PLA tokens, valuing a massive $31M loss. A significant portion, $5.9M worth, found its way to the Gate platform. The exploit was due to a security vulnerability. @EthSecurity1
πŸ”₯3😁2😱2