Security

2 Altcoin Phishing Incidents Result in Significant Losses, Says PeckShieldAlert

Recently, a couple of phishing events have taken place. As per PeckShieldAlert, a prominent company offering data and security analytics about blockchain, altcoin phishing incidents have resulted in huge losses for the impacted addresses. The platform took to its official social media account to provide the details of these phishing scams.

#PeckShieldAlert #Phishing An address 0x73A0…52DF has fallen victim to phishing by #Fake_Phishing361733, resulting in a loss of 61 $WETH (worth ~$213K) pic.twitter.com/N4SSktxn8E

— PeckShieldAlert (@PeckShieldAlert) July 21, 2024

Altcoin Phishing Attacks Result in Enormous Losses PeckShieldAlert Asserts

In its latest 2 X posts, the firm revealed that the address “0x73A0…52DF” experienced the scam in one attempt. According to PeckShieldAlert, the phishing scam goes by the label “#Fake_Phishing361733.” This event paved the way for the loss of nearly 61 $WETH. This figure equals almost $213,000. The respective incident indicates the present hazard of phishing incidents in the crypto sector.

The Attackers Take Away $213,000 and $87,000 Worth of $WETH and $TYPE Coins

The malicious actors trick the unsuspecting consumers into sharing private keys as well as the rest of the sensitive information. This permits the exploiters to illegally access the funds of their victims. The 2nd incident comprised another address. In this case, the address “0xe7e9…fa01” experienced a different phishing event. The respective incident goes by “#Fake_Phishing187019.

As a result of this phishing scam, the victim reportedly lost up to 114,138.9 $TYPE coins. The respective tokens had a value of approximately $87,000. Analogous to the former event, this phishing scam potentially comprised deceptive tactics. In this way, the exploiter likely convinced the victim to carry out actions, compromising security.

Source

Click to rate this post!
[Total: 0 Average: 0]
Show More

Leave a Reply

Your email address will not be published. Required fields are marked *