AmineElmerzouki
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
![image](https://hackmd.io/_uploads/rk5cVFvI6.png) # Address Poisoning: A Rising Threat in the Cryptocurrency Space ## Introduction to Address Poisoning Address Poisoning is a relatively new but increasingly prevalent scam in the cryptocurrency world. This scam exploits a common user behavior in the crypto community: copying and pasting wallet addresses. Due to the complexity and length of blockchain addresses, most users rely on copying and pasting these addresses for transactions. Scammers take advantage of this by creating wallet addresses that closely resemble legitimate ones, tricking users into sending funds to the wrong address. ## Mechanism of the Attack: Understanding Address Poisoning in Crypto Wallets Address poisoning is a sophisticated scam targeting cryptocurrency users, particularly those using Ethereum and Ethereum Virtual Machine (EVM) compatible blockchains like Binance Smart Chain and Polygon. The mechanism behind this attack is both cunning and simple, exploiting the general user behavior of copying and pasting wallet addresses for transactions. ### Targeting EVM-Compatible Blockchains Scammers specifically target users of EVM-compatible blockchains due to their popularity and widespread use. These platforms, known for their low transaction fees, are ideal for scammers as they can execute their fraudulent activities on a large scale without incurring significant costs. ### The Creation of Vanity Addresses The core strategy in address poisoning involves the creation of what is known as a "vanity address." This is a custom-made address that closely resembles the victim's own wallet address. The attacker meticulously crafts these addresses to have a specific set of characters that match the beginning or end of the target's genuine address. To an unsuspecting eye, these addresses appear almost identical to the legitimate ones. ### Exploiting User Behavior Once the vanity address is created, the scammer then initiates a small transaction, sending a negligible amount of cryptocurrency to the victim's wallet from this fraudulent address. This action poisons the victim’s transaction history, embedding the vanity address among legitimate transactions. ### The Risk in Transaction Histories The danger arises when users, following their usual practice, copy an address from their transaction history for a new transaction. In the haste of operations and due to the striking similarity, there is a high likelihood of copying the vanity address instead of the intended one. When the victim executes the transaction, their assets are inadvertently sent to the scammer's address. ### Safety of Assets and Private Keys It's important to note that while address poisoning poses a significant risk to the assets being transferred, it does not compromise the safety of the assets stored in the wallet or lead to the leakage of private keys. The attack is purely based on deceiving the user into sending funds to the wrong address. ### Prevalence on Various Blockchains While this type of attack can occur on any blockchain, scammers often choose networks like Polygon, Avalanche, and Binance Smart Chain for their lower transaction fees. These blockchains' cost-effectiveness allows scammers to target a vast number of addresses without incurring substantial expenses. ### Public Nature of Blockchains The public nature of blockchains plays into the hands of these scammers. Since all addresses and transactions are a matter of public record, it is relatively easy for attackers to scan block explorers, identify a large number of active addresses, and send spoofed transactions to them. This broad targeting increases the chances of successful deception. In summary, address poisoning exploits common user behaviors in the cryptocurrency realm, leveraging the subtle manipulation of wallet addresses to misdirect funds. The attack is a stark reminder of the importance of vigilance and meticulous verification in all crypto transactions. ## What is SAFE Wallet? ![image](https://hackmd.io/_uploads/HJ6nsww86.png) https://app.safe.global/ SAFE Wallet is a MultiSig wallet tailored for decentralized co-management of digital assets. It offers self-custody, mitigating risks associated with traditional banking systems. The wallet is designed for DAOs, groups, and enterprises, ensuring security through a multi-signature system. This system requires a consensus among multiple stakeholders for transactions, enhancing security over single-key wallets. ### Key Features Multi-Signature Security: Requires multiple approvals for transactions, protecting against unauthorized access. * **Transaction Batching**: Enables sending multiple transactions simultaneously. * **Fraud Monitoring**: Provides additional security against fraudulent activities. * **DeFi Compatibility**: Allows interaction with decentralized finance platforms. ### User Accessibility SAFE Wallet is accessible to a broad range of users, including individuals, financial institutions, and various groups. ### Setting Up To create a SAFE account, users connect a signer wallet and then proceed to set up the SAFE Wallet by selecting "Create New Safe" and naming their Safe. This name is stored locally for privacy. In summary, SAFE Wallet is a robust platform for secure, decentralized asset management, suitable for a variety of users. ## Address Poisoning Against SAFE Wallet SAFE Wallet users have been the victims of significant address poisoning attacks, with over $5 million stolen from 21 victims in just four months. In these attacks, scammers created wallet addresses similar to those of the victims. They then sent small amounts of cryptocurrency from these fraudulent addresses to the victims' wallets. When the victims later attempted to make transactions, they mistakenly copied the scammer's address and sent large sums to the wrong recipient. ## Example of an Address Poisoning Attack An example of this attack can be seen in a tweet from [Scam Sniffer's Twitter](https://twitter.com/realScamSniffer/status/1731867457521066042). In this tweet, Scam Sniffer highlights a particular instance of address poisoning, providing insight into how these scams are orchestrated and the devastating impact they can have on unsuspecting victims. <blockquote class="twitter-tweet"><p lang="en" dir="ltr">another Safe Wallet lost $30k to an &quot;address poisoning&quot; attack about 10 hours ago.<br><br>the victim&#39;s transfer history was contaminated by the attacker 12 days ago.<a href="https://t.co/ANJfKYQ3is">https://t.co/ANJfKYQ3is</a> <a href="https://t.co/KVzExnOnfS">https://t.co/KVzExnOnfS</a> <a href="https://t.co/7sTSL1jlyS">pic.twitter.com/7sTSL1jlyS</a></p>&mdash; Scam Sniffer | Web3 Anti-Scam (@realScamSniffer) <a href="https://twitter.com/realScamSniffer/status/1731867457521066042?ref_src=twsrc%5Etfw">December 5, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> ![image](https://hackmd.io/_uploads/SkpffYwI6.png) ![image](https://hackmd.io/_uploads/r1WkfYDU6.png) ![image](https://hackmd.io/_uploads/rJxminOL6.png) ## Conclusions and Recommendations To combat address poisoning, users must be vigilant and adopt safer transaction practices. This includes double-checking every character of the recipient's address, using address book features in crypto wallets, employing hardware wallets for added security, and considering test transactions for large sums. Staying informed about the latest scams in the cryptocurrency space is also crucial for protection. While address poisoning is a sophisticated scam, awareness and careful transaction habits can significantly reduce the risk of falling victim to it.However, users can take several steps to protect themselves: 1. **Double-Check Addresses**: Always verify every character of the recipient's address before making a transaction. This is the most reliable way to avoid falling for an address poisoning scam. 2. **Use Address Book Features**: Most crypto wallets offer an address book where you can save trusted addresses. Using saved addresses instead of copying from transaction histories can significantly reduce the risk of copying a poisoned address. 3. **Hardware Wallets**: Using a hardware wallet can add an extra layer of security. These wallets often require users to confirm addresses on the device itself, which can help in catching a poisoned address. 4. **Test Transactions**: Sending a small amount first and confirming its receipt can be an effective, albeit sometimes costly, way to ensure the correctness of the recipient address. 5. **Stay Informed**: Regularly updating oneself on the latest scams and security practices in the crypto space is crucial for staying safe Address poisoning highlights the need for vigilance in the cryptocurrency space. Users should always be cautious and double-check every transaction detail, as the decentralized nature of cryptocurrencies means that transactions are irreversible and lost funds may not be recoverable.

Import from clipboard

Paste your webpage below. It will be converted to Markdown.

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully