Binance Square
#peckshield

peckshield

15,526 views
28 Discussing
Doctor media
·
--
🚨 $8.5 MILLION RETURNED: THE 75% HACKER BOUNTY GAME! 🚨 A massive twist in the Verus Bridge exploit! The attacker has officially returned 4,052 $ETH ($8.5M) after draining $11.58M from the protocol. $BEAT $AGT $ZEC Per PeckShield, the returned funds represent 75% of the stolen assets. The remaining 25%—1,350 $ETH ($2.8M)—is being kept by the exploiter as a massive "white hat" bounty. The negotiation worked, and 75% of the protocol's funds are officially safe! 💸🛡️ Is a 25% bounty too high, or a fair price for recovery? 👇 #Ethereum #ETH #VerusBridge #PeckShield #BinanceSquare
🚨 $8.5 MILLION RETURNED: THE 75% HACKER BOUNTY GAME! 🚨
A massive twist in the Verus Bridge exploit! The attacker has officially returned 4,052 $ETH ($8.5M) after draining $11.58M from the protocol.
$BEAT $AGT $ZEC
Per PeckShield, the returned funds represent 75% of the stolen assets. The remaining 25%—1,350 $ETH ($2.8M)—is being kept by the exploiter as a massive "white hat" bounty.
The negotiation worked, and 75% of the protocol's funds are officially safe! 💸🛡️
Is a 25% bounty too high, or a fair price for recovery? 👇
#Ethereum #ETH #VerusBridge #PeckShield #BinanceSquare
Across Protocol attackers have returned 331.8 ETH (about $623,900) to a multisig address controlled by the Across Protocol Hub Pool owner. On the surface, this looks like stop-loss progress; what’s really worth discussing is the return recipient: The funds are flowing back to a multisig address, not directly to the user side. That means the real risk lies in how the funds will be allocated afterward, how the accounting will be done, and who will confirm the loss amount. The attacker’s willingness to return about $623,900 usually suggests the incident is more like a negotiable security matter rather than a completely out-of-control token theft and exit. However, the news does not specify the vulnerability type, the total loss, or whether the full amount was returned, so the market can’t simply treat this as risk fully resolved. More subtly, PeckShield disclosed the details before the project itself. This may force Across to complete the missing details with a more transparent incident report. If the project only emphasizes that the funds were returned while avoiding the attack path, that’s the red flag traders should watch for. For ACX traders, the short-term issue isn’t really those 331.8 ETH—it’s instead: whether there are additional returns afterward, whether the relevant cross-chain routes are paused, and whether liquidity providers have started to withdraw. Do you think that after a cross-chain protocol is hacked, returned funds can restore trust? #AcrossProtocol #ACX #跨链安全 #PeckShield #Attack
Across Protocol attackers have returned 331.8 ETH (about $623,900) to a multisig address controlled by the Across Protocol Hub Pool owner.

On the surface, this looks like stop-loss progress; what’s really worth discussing is the return recipient:

The funds are flowing back to a multisig address, not directly to the user side. That means the real risk lies in how the funds will be allocated afterward, how the accounting will be done, and who will confirm the loss amount.

The attacker’s willingness to return about $623,900 usually suggests the incident is more like a negotiable security matter rather than a completely out-of-control token theft and exit. However, the news does not specify the vulnerability type, the total loss, or whether the full amount was returned, so the market can’t simply treat this as risk fully resolved.

More subtly, PeckShield disclosed the details before the project itself. This may force Across to complete the missing details with a more transparent incident report. If the project only emphasizes that the funds were returned while avoiding the attack path, that’s the red flag traders should watch for.

For ACX traders, the short-term issue isn’t really those 331.8 ETH—it’s instead: whether there are additional returns afterward, whether the relevant cross-chain routes are paused, and whether liquidity providers have started to withdraw.

Do you think that after a cross-chain protocol is hacked, returned funds can restore trust?

#AcrossProtocol #ACX #跨链安全 #PeckShield #Attack
Important security warning for the crypto community: The Gnosis account on platform X may currently be under the control of hackers. PeckShield, a cybersecurity firm, has sounded the alarm after noticing suspicious activity on the account. If you're following this, extreme caution is required right now; do not click on any links posted from the account, and refrain from interacting with any new tweets until an official clarification from the team is issued. Here's what you need to do immediately: Avoid clicking on any Gnosis-related links on platform X. Ignore any offers or wallet connection requests popping up through the hacked account. Keep an eye on other official channels of the project for reliable updates. Always remember that security starts with proactive steps from you. Have you recently encountered similar phishing attempts in other projects? How do you protect yourself from these malicious links? Share your thoughts and experiences in the comments, and don't forget to retweet to alert your friends in the community. 🛡️⚠️ $GNO {spot}(GNOUSDT) #Gnosis #CryptoSecurity #PeckShield #Blockchain #CyberSecurity #Web3 #CryptoNews
Important security warning for the crypto community: The Gnosis account on platform X may currently be under the control of hackers.

PeckShield, a cybersecurity firm, has sounded the alarm after noticing suspicious activity on the account. If you're following this, extreme caution is required right now; do not click on any links posted from the account, and refrain from interacting with any new tweets until an official clarification from the team is issued.

Here's what you need to do immediately:

Avoid clicking on any Gnosis-related links on platform X.

Ignore any offers or wallet connection requests popping up through the hacked account.

Keep an eye on other official channels of the project for reliable updates.

Always remember that security starts with proactive steps from you. Have you recently encountered similar phishing attempts in other projects? How do you protect yourself from these malicious links?

Share your thoughts and experiences in the comments, and don't forget to retweet to alert your friends in the community. 🛡️⚠️
$GNO

#Gnosis #CryptoSecurity #PeckShield #Blockchain #CyberSecurity #Web3 #CryptoNews
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number