Test

when

Security

<div class="wublock">
 <div dir="auto" class="body markup">
 <div class="captioned-image-container">
 <figure>
 <div class="image2-inset">
 <picture>
 <source type="image/webp" srcset="https://substackcdn.com/image/fetch/w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 424w, https://substackcdn.com/image/fetch/w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 848w, https://substackcdn.com/image/fetch/w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 1272w, https://substackcdn.com/image/fetch/w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 1456w" sizes="100vw">
 <img src="https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:649384,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:null}" class="sizing-normal" alt srcset="https://substackcdn.com/image/fetch/w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 424w, https://substackcdn.com/image/fetch/w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 848w, https://substackcdn.com/image/fetch/w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 1272w, https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F520c778b-739f-4b87-9a8d-a3f8f547dca3_5999x3999.jpeg 1456w" sizes="100vw" fetchpriority="high">
 </picture>
 <div class="image-link-expand">
 <svg xmlns="//www.w3.org/2000/svg" width="20" height="20" viewbox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 ">
 <polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line>
 </svg>
 </div>
 </div>
 </figure>
 </div>
 Author: 胡飞瞳
 Source: https://mp.weixin.qq.com/s/jCtgFy5e5o3TxmHTOk_rLQ
 On the evening of May 3rd, Beijing time, due to an inadvertent operation, a whale mistakenly transferred 1155 BTC to a phishing wallet address, valued at approximately $71 million at the time of the incident. Such a large sum of money virtually evaporated in an instant, serving as a significant lesson to the industry.
 Chronology of Events
 Let’s first examine the sequence of events (May 3rd, all times in Beijing time):
 ● 17:14:47 — Wallet address 0x1E227979f0b5BC691a70DEAed2e0F39a6F538FD5 (whale) transferred 0.5 ETH to address 0xd9A1b0B1e1aE382DbDc898Ea68012FfcB2853a91 and created the address.
 ● 17:17:59 — Wallet address 0xd9A1C3788D81257612E2581A6ea0aDa244853a91 (hacker) transferred 0 ETH to wallet address 0x1E227979f0b5BC691a70DEAed2e0F39a6F538FD5.
 ● 18:31:35 — Wallet address 0x1E227979f0b5BC691a70DEAed2e0F39a6F538FD5 (whale) transferred 1155.28802767 WBTC to address 0xd9A1C3788D81257612E2581A6ea0aDa244853a91 by calling the WBTC contract.
 ● May 4th, 10:51:11 — Address 0xd9A1C3788D81257612E2581A6ea0aDa244853a91 (hacker) transferred all WBTC to a new address: 0xfB5bcA56A3824E58A2c77217fb667AE67000b7A6.
 Explanation
 Here’s a breakdown from the hacker’s perspective:
 1. The hacker continuously monitored the whale’s activity on the blockchain and noticed the creation of a new address by the whale on the evening of May 3rd. The hacker immediately took action.
 2. By bruteforce-randomly generating private keys and addresses, the hacker obtained an address similar to the one generated by the whale (please carefully examine the addresses highlighted in red in steps 1 and 2 above, they are identical except for minor differences). The hacker then transferred 0 ETH to the whale’s wallet address to create a transaction history containing the phishing address 0xd9A1C3788D81257612E2581A6ea0aDa244853a91.
 3. Upon confirming the receipt of 0.5 ETH in their address, the whale began transferring WBTC to a new address. At this point, a fatal mistake occurred. In the transfer history, the whale found an address with the same numbers before and after as their target address and mistakenly copied and pasted the phishing address.
 4. The hacker monitored their phishing address and was pleasantly surprised to find a “huge harvest” — 1155 BTC. They likely celebrated immediately, had some beers, slept, and then transferred the WBTC to another new address.
 Implications
 Have you noticed a crucial aspect? Look at the timeline. After the whale created a new address, the hacker prepared the phishing address in about 3 minutes and completed the transfer to the whale. This indicates several points:
 ● The hacker was well-prepared, with the entire <a rel="dofollow" title="process" href="https://thebittimes.com/tag/process.html">process</a> automated. The script was likely prepared in advance.
 ● The hacker had access to significant computational power. The addresses generated here share specific bytes (the first two bytes and the last three bytes), which equates to roughly 2⁴⁰ calculations. GPUs would undoubtedly be required, and in large numbers.
 ● Therefore, this is likely not an individual’s action but rather organized behavior.
 The blockchain brings decentralization and eliminates intermediaries, allowing individuals to control their wealth and data. However, it also requires a heightened sense of security. High levels of personal security awareness and knowledge are essential.
 This whale demonstrated strong security awareness by periodically changing addresses and conducting tests and confirmations before large transfers. However, one copy-paste mistake undid everything.
 Some Security Tips for Transfers
 This $71 million lesson serves as a wake-up call for every holder of digital assets. Hackers and phishing attempts are ubiquitous, and you are the first and only responsible party for your property. Here are some security tips for wallet security, especially for wallets holding large amounts:
 ● Generate private keys and mnemonic phrases offline and store them offline.
 ○ Most wallets now have offline signature capabilities.
 ○ Hardware wallets can also be used, but backup the private keys when using them.
 ● If there is suspicion that the private key or mnemonic phrase may be compromised, replace it as soon as possible and transfer the assets.
 ● Store transfer addresses in an address book and add notes. Do not copy addresses temporarily.
 ● Choose addresses from the address book for transfers and always perform test transfers. Confirm success with the recipient before proceeding.
 ● For large transfers, consider splitting them into multiple transactions.
 ● Do not click directly on transfer links or online transactions sent by others.
 ○ Phishing often involves forging similar links or addresses.
 ● For larger fund management, consider using multi-signature methods.
 ○ This is suitable for company or organization fund management.
 ○ Individual assets can also be managed in this way. For example, individuals can hold multiple private keys and give signing authority to friends who do not know each other to prevent loss of assets due to personal key loss.
 ● CEX and DEX website addresses should be obtained through official channels, and deposit addresses should be confirmed repeatedly. Test transfers are also necessary steps.
 Follow us Twitter: https://twitter.com/WuBlockchain Telegram: https://t.me/wublockchainenglish
 </div>
</div>
Source: <a rel="dofollow" target="_blank" href="https://thebittimes.com/the-whole-process-how-to-lose-1155-btc-in-80-minutes-tbt88529.html">https://thebittimes.com/the-whole-process-how-to-lose-1155-btc-in-80-minutes-tbt88529.html</a>

The whole process: How to Lose 1155 BTC in 80 Minutes

TheBitTimes

Other articles published on May 16, 2024

MEME Coin Season Arrived; Roaring Kitty Brings Tsunami of Gains

Fantom & Near Protocol Soar As Bitcoin Display Strength, Will FTM & NEAR Price Maintain a Bullish...

Secret Network Tackles Crypto’s Key Issues: Privacy & RWAs

Shiba Inu Whale Alert: $75 Million SHIB Move to Robinhood Sparks Market Surge, SHIB Price Up By 1...

Mastercard’s Start Path Adds 5 Blockchain Startups

U.S. Presidential Debates Boost MAGA Memecoin, BODEN: 'Attention Is Starting And Getting Hot,' Tr...

Join our free newsletter for daily crypto updates!