Whitehat
@TokenLith
Followers
1
Following
38
Media
0
Statuses
25
Joined July 2023
@PrismaFi faced an $11.6M exploit, but white hat hackers returned the funds after negotiating a bounty through a rescue operation. Understanding the hack's root causes is crucial to prevent future incidents. Read more about the $11M hack breakdown
techfund.jp
最近、@PrismaFiがホワイトハットハッカーに悪用(または侵害)された。専門用語は重要ではありませんが、最も重要なのはこの事件から学ぶことです。概要この脆弱性は、BorrowerOperation...
1
4
22
Really learn alot from this breakdown
@PrismaFi faced an $11.6M exploit, but white hat hackers returned the funds after negotiating a bounty through a rescue operation. Understanding the hack's root causes is crucial to prevent future incidents. Read more about the $11M hack breakdown
0
0
0
Startup idea: Establish a CISO-as-a-Service company. With companies increasingly seeking to hire full-time security specialists, offering expert CISOs to their teams would definitely make this idea successful.
0
1
5
#Security Alert: Understanding the $8.5 Million WOOFi Exploit On Mar 5th, WOOFi encountered a devastating flash loan attack on the Arbitrum network, resulting in loss of $8.5 million. Here's a breakdown of what happened & how you can prevent it : https://t.co/bpo8VjYJv6
techfund.jp
WOOFi、Arbitrumで850万ドルのフラッシュローン攻撃を受ける(3月5日) 概要3月5日、さまざまなブロックチェーンで運営されている有名な分散型取引所(DEX)であるWOOFiが、...
0
3
6
Here is a brief explanation of the recent $8.5 million #Woofi hack. Learn from it and avoid making the same mistake in your contracts
#Security Alert: Understanding the $8.5 Million WOOFi Exploit On Mar 5th, WOOFi encountered a devastating flash loan attack on the Arbitrum network, resulting in loss of $8.5 million. Here's a breakdown of what happened & how you can prevent it : https://t.co/bpo8VjYJv6
0
1
5
🫡
A few hours ago, a @minerercx exploited a vulnerability resulting in a loss of $456k. The vulnerability lies in the `_update` function. If a user transfers tokens to themselves within the same transaction, there is indeed a potential for their balance to double. This scenario
0
0
0
In the recent Future Crime Summit 2024, I had the opportunity to meet some of the biggest minds of the Indian government, which was really insightful for me. I learned a lot from them. However, I noticed that many professors from institutes were also attending to explore new
0
1
6
#Caution: Recently, many malicious links have been circulating, claiming to be associated with @alt_layer token distribution. These links are fully malicious; never click on them. The sender's email address is hijabi.pk1@gmail.com.
0
0
0
Cloud security is as crucial as the security of your smart contracts. Always prioritize securing both Web 2 and Web 3 components. Recently, Ukrainian hackers executed 1500 different brute force attacks to compromise a cloud server, resulting in the theft of millions in crypto
2
1
3
🚨 Security Breach Update 🚨: https://t.co/NDGHDA4704 on Arbitrum recently suffered a $1.7M hit in a cunning social engineering attack. Here's a breakdown: The attacker slyly altered the CONE-1 proxy contract, swapping it from ConeCamelotVault to their controlled contract.
2
3
5
it is a biggest hack of 2024 ??
🚨 Security Alert 🚨 @GAMEEToken has experienced a security breach! Unauthorized deployer key access led to an attack using the recoverERC721s() function, bypassing $GMEE recovery protection. Approximately 600m $GMEE has been drained from the contract. 🔗 Attack transactions:
0
0
0
🚨 SECURITY ALERT 🚨 @samudaixyz has fallen victim to a significant security breach, resulting in the loss of $1.2M worth of ETH from both the founder's and multisig wallets. 🔍 Investigation is underway, and the community is urged to report any suspicious activity related to
1
3
5
huge security breach
🚨 SECURITY ALERT 🚨 @samudaixyz has fallen victim to a significant security breach, resulting in the loss of $1.2M worth of ETH from both the founder's and multisig wallets. 🔍 Investigation is underway, and the community is urged to report any suspicious activity related to
0
0
0
🚨 #SocketProtocol Update 🚨 @SocketDotTech fell prey to a call injection attack, resulting in a staggering loss of $3.3M. The breach's epicenter lies in an insecure call within the performAction function. Overlooking scenarios with 0 WETH transfers allowed the attacker to
3
3
5