Ethereum Address Poisoning Attack Escalates: After One Transfer, He Received 89 Alert Emails

marsbitОпубликовано 2026-03-13Обновлено 2026-03-13

Введение

Ethereum address poisoning attacks have evolved into a highly automated and industrialized threat, as highlighted by a user who received 89 alert emails after just two legitimate stablecoin transfers. Attackers monitor blockchain activity to identify targets, then generate and send fake addresses with similar starting and ending characters to the victim’s transaction history, aiming to trick users into copying the wrong address in future transactions. A 2025 study revealed that between July 2022 and June 2024, Ethereum saw 17 million poisoning attempts affecting 1.3 million users, causing at least $79.3 million in losses. The problem has intensified since the Fusaka upgrade in December 2025, which reduced transaction fees and enabled attackers to scale poisoning efforts—evidenced by a massive increase in dust transactions (e.g., USDT dust transfers surged 612%). The core defense remains vigilance: always verify addresses before sending funds. Use tools like Etherscan’s address labels, ENS domains, and address highlighting to distinguish legitimate addresses. Enable wallet whitelisting and heed warnings when copying suspicious addresses. As transactions become cheaper and attacks more frequent, user awareness and improved interface designs are critical to mitigating risks.

Written by: etherscan.eth

Compiled by: AididiaoJP, Foresight News

A few weeks ago, an Etherscan user named Nima shared an unpleasant experience. After completing just two stablecoin transfers, he received over 89 address monitoring alert emails in a short period.

As Nima pointed out, these alerts were triggered by address poisoning transactions. The sole purpose of these transactions, created by attackers, is to implant highly similar fake addresses into the user's transaction history, intending to trick the user into mistakenly using these fake addresses when copying for their next transfer.

Address poisoning has existed on Ethereum for years. However, such incidents highlight that these attack campaigns have become highly automated and scaled. What was once sporadic spam is now executed on a massive scale, with attackers often implanting poisoning transfers within minutes of a legitimate transaction occurring.

To understand why such attacks have become more prevalent, we need to analyze two dimensions: the evolution of address poisoning attack methods, and the fundamental reasons why they can be easily operated at scale.

Additionally, this article will focus on explaining a core prevention principle to help users effectively defend against such attacks.

I. The Industrialization of Address Poisoning

Address poisoning was once considered a niche fraudulent tactic used by opportunistic attackers. However, today, its operational model increasingly exhibits industrial characteristics.

A study published in 2025, analyzing address poisoning activities between July 2022 and June 2024 (i.e., before the Fusaka upgrade), showed that there were approximately 17 million poisoning attempts on Ethereum, involving about 1.3 million users, with confirmed losses of at least $79.3 million.

The table below, based on results from the "Blockchain Address Poisoning Research," shows the scale of address poisoning activities on Ethereum and BSC between July 2022 and June 2024. The data indicates that on the BSC chain, where transaction fees are significantly lower, the frequency of poisoning transfers was 1355% higher.

Attackers typically identify potential targets by monitoring blockchain activity. Once a target user's transaction is detected, automated systems generate highly similar addresses that share the same starting and ending characters as the legitimate addresses the user has interacted with. The attackers then send poisoning transfers containing these fake addresses to the target address, causing them to appear in the user's transaction history.

Attackers tend to target addresses with higher profit potential. Addresses that frequently make transfers, hold large token balances, or participate in large-value transfers typically receive more poisoning attempts.

Competition Mechanism Enhances Attack Efficiency

The 2025 study revealed a noteworthy phenomenon: different attack groups often compete with each other. In many poisoning campaigns, multiple attackers send poisoning transfers to the same target address almost simultaneously.

Each attack group attempts to be the first to implant their fake address into the user's transaction history, hoping that their address will be selected first when the user copies an address later. The one who successfully implants first has an increased probability of having their fake address mistakenly copied by the user.

The case of the following address fully demonstrates the intensity of this competition. In this case, within minutes of a legitimate USDT transfer being completed, 13 poisoning transactions were implanted.

Note: Etherscan hides zero-value transfers by default; hidden items have been unhidden here for demonstration purposes

Common methods used in address poisoning attacks include: dust transfers, fake token transfers, and zero-value token transfers.

II. Reasons Why Address Poisoning Attacks Are Easy to Scale

At first glance, the success rate of address poisoning seems low. After all, most users are not fooled. However, from an economic perspective, the logic of such attacks is quite different.

The Logic of a Probability Game

Researchers found that the success rate of a single poisoning attempt on Ethereum is approximately 0.01%. In other words, out of every 10,000 poisoning transfers, only about 1 might lead to a user mistakenly sending funds to the attacker.

Given this, poisoning campaigns are no longer limited to a few addresses but tend to send thousands or even millions of poisoning transfers. When the attempt base is large enough, even a tiny success rate can accumulate to generate considerable illegal profits.

A single successful large-value transfer fraud can easily cover the costs of thousands of failed attempts.

Lower Transaction Costs Stimulate Increase in Poisoning Attempts

The Fusaka upgrade, activated on December 3, 2025, introduced scalability optimizations that effectively reduced transaction costs on Ethereum. While benefiting ordinary users and developers, this change also significantly lowered the cost for attackers to initiate a single poisoning transfer, enabling them to send poisoning attempts on an unprecedented scale.

After the Fusaka upgrade, Ethereum network activity increased markedly. In the 90 days post-upgrade, the average daily transaction processing volume increased by 30% compared to the 90 days pre-upgrade. During the same period, the average daily number of newly created addresses increased by about 78%.

Furthermore, we observed a significant increase in dust transfer activity. In these transfers, attackers send transactions involving the same token as in the user's history but for a very small amount.

The data below compares dust transfer activity for several major assets in the 90 days before and after the Fusaka upgrade. For stablecoins like USDT, USDC, and DAI, dust transfers refer to transactions below $0.01; for ETH, it refers to transfers below 0.00001 ETH.

USDT

  • Pre-upgrade: 4.2 million
  • Post-upgrade: 29.9 million
  • Increase: +25.7 million (+612%)

USDC

  • Pre-upgrade: 2.6 million
  • Post-upgrade: 14.9 million
  • Increase: +12.3 million (+473%)

DAI

  • Pre-upgrade: 142,405
  • Post-upgrade: 811,029
  • Increase: +668,624 (+470%)

ETH

  • Pre-upgrade: 104.5 million
  • Post-upgrade: 169.7 million
  • Increase: +65.2 million (+62%)

The data indicates that shortly after the Fusaka upgrade, dust transfer activity (below $0.01) surged sharply, peaked, and then declined somewhat, but remained significantly higher than pre-upgrade levels. In contrast, transfer activity above $0.01 remained relatively stable during the same period.

Chart: Comparison of dust transfer trends (<$0.01) for USDT, USDC, and DAI in the 90 days before and after the Fusaka upgrade

<极>

Chart: Comparison of regular transfer trends (>$0.01) for USDT, USDC, and DAI in the 90 days before and after the Fusaka upgrade

In many attack campaigns, attackers first bulk-send tokens and ETH to newly generated fake addresses, which then send dust transfers one by one to the target addresses. Since dust transfers involve extremely low amounts, with lower transaction costs, attackers can operate on a massive scale at very low cost.

Illustration: Address Fake_Phishing1688433 bulk-sending tokens and ETH to multiple different fake addresses in one transaction

It is important to clarify that not all dust transfers are poisoning acts. Dust transfers can also originate from legitimate activities, such as token airdrops or小额 interactions between addresses. However, after reviewing a large number of dust transfer records, it can be judged that a significant portion of them are highly likely to be poisoning attempts.

III. Core Prevention Principle

Always carefully verify the destination address before sending any funds.

Here are some practical suggestions for reducing risk when using Etherscan:

Use Identifiable Address Labels

For addresses you frequently interact with, set private name tags on Etherscan. This helps make legitimate addresses clearly distinguishable among many similar addresses.

Using domain name services like ENS can also improve the recognizability of addresses throughout the browser.

It is also recommended to use the wallet's address book feature to whitelist commonly used addresses, ensuring funds are always sent to the intended target.

Enable Address Highlighting

Etherscan's address highlighting feature helps users visually distinguish between visually similar addresses. If two addresses look almost identical but are highlighted differently, one is highly likely to be a poisoning address.

Always Double-Check Before Copying an Address

Etherscan proactively pops up提醒 windows when users copy addresses that may be associated with suspicious activity. This suspicious activity includes:

  • Low-value token transfers
  • Fake token transfers
  • Tokens with poor reputation
  • Tokens with outdated information

When you see such a reminder, be sure to pause and carefully verify whether the address you are copying is the target address you真正 intend to interact with.

Remember, there is no "undo" button in the crypto world. Once funds are sent to the wrong address, the possibility of recovery is minimal.

Summary

As lower costs make high-volume attack strategies more economical, address poisoning attacks on Ethereum are becoming increasingly rampant. Such attacks also negatively impact the user experience, with大量 poisoning spam cluttering transaction history interfaces面向 users.

Effectively preventing address poisoning attacks requires both users to improve their own security awareness and better interface design support. For users, the most crucial habit to develop is: always carefully verify the destination address before sending funds.

At the same time, related tools and user interfaces should play a greater role in helping users quickly identify suspicious activity.

Poisoning address label on Etherscan (https://etherscan.io/accounts/label/poisoning-address)

Etherscan is continuously committed to improving the browser interface and API services to help users more easily identify such attacks. We proactively label fake addresses, identify and hide zero-value token transfers, and label fake tokens. By providing this curated data, users can more easily spot potential address poisoning attempts without manually sifting through massive transaction records.

As poisoning attacks escalate with automation and high-volume dust transfer methods, clearly presenting these risk signals is crucial to helping users distinguish between suspicious activity and legitimate transactions.

Связанные с этим вопросы

QWhat is address poisoning in the context of Ethereum, and how does it work?

AAddress poisoning is a scam where attackers send transactions to a user's address using a fake address that looks very similar to a legitimate one the user has previously interacted with. The goal is to implant this fake address into the user's transaction history, hoping the user will mistakenly copy and send funds to it in the future.

QAccording to the article, how has the Fusaka upgrade on Ethereum impacted address poisoning attacks?

AThe Fusaka upgrade, which lowered transaction costs on Ethereum, made it significantly cheaper for attackers to launch address poisoning attempts. This led to a massive increase in dust transactions (transfers of tiny amounts of tokens), which are often used in these attacks, as attackers could operate on a much larger scale.

QWhat is the estimated success rate of an address poisoning attack on Ethereum, and why do attackers still pursue it?

AThe estimated success rate of a single address poisoning attempt on Ethereum is about 0.01%. Attackers still pursue it because it is a numbers game. By sending thousands or millions of attempts, the small success rate can accumulate into substantial illegal profits, as one successful large transfer can easily cover the cost of thousands of failed attempts.

QWhat is the single most important principle for users to protect themselves from address poisoning?

AThe single most important principle is to always carefully verify the destination address before sending any funds. Users should double-check the full address and not rely solely on the first and last few characters.

QWhat are some specific tools or features on Etherscan that can help users identify and avoid poisoned addresses?

AEtherscan offers several features to help users: Address Highlighting to visually distinguish between similar-looking addresses, Private Name Tags and ENS names to make legitimate addresses easily identifiable, an Address Book for whitelisting trusted addresses, and Warning Pop-ups that appear when a user attempts to copy an address associated with suspicious activity like low-value token transfers.

Похожее

It Took Me a Year to See the Bitter Truth About Agent Payments

After a year building infrastructure for the Agent economy, engaging with major players like Stripe, Visa, and Coinbase, the author shares a sobering analysis of the current state of Agent payments. The core finding is a stark lack of genuine, immediate demand across most envisioned use cases. The article breaks down four key market segments: 1. **Agent-to-Merchant (Consumer Shopping):** For most product categories (e.g., clothing, electronics), conversational AI shopping is a step backwards from visual e-commerce interfaces. While agents excel at understanding needs, they can't replace side-by-side product comparison. Real merchant interest is defensive "Agent Engine Optimization," not driven by current customer demand. Potential exists for high-frequency, low-decision purchases (like food delivery) or navigating complex store UIs, but these require massive B2C distribution channels dominated by giants like Amazon. 2. **Agent-to-API (Developer Services):** Developers already have subscriptions and billing relationships for APIs (compute, data). Prepaid balances solve micro-payment issues for low transaction volumes. A deeper structural problem is that major SaaS vendors' business models rely on enterprise contracts, resisting granular pay-per-call pricing. While protocols like MPP and x402 serve the long tail of niche services, this market is small and developers are historically low-willingness-to-pay. 3. **Agent-to-Agent:** This remains largely theoretical with minimal transaction volume. While it represents a long-term bet on a fundamentally new transaction infrastructure (sub-second, micro-penny to million-dollar, multi-party settlements), it does not constitute a present market. 4. **Agent-to-Finance:** This is the only category with existing, paying demand. Integrating AI into financial workflows (trading, portfolio management) is a natural evolution and enables new capabilities like autonomous rebalancing. However, competition favors established, regulated institutions. The "real problem" is not moving money between agents, but the broader challenge of **coordination**—orchestrating work between agents and humans, verifying outcomes, and settling results. Payment is just one component of settlement, which is itself part of coordination. Companies that solve the coordination layer will subsume payment, not the other way around. While well-funded incumbents build defensively for a long-term future, startups must find where the market is today—which, for the author's team, lies outside these four categories in an area of real, growing, and underserved activity.

marsbit7 мин. назад

It Took Me a Year to See the Bitter Truth About Agent Payments

marsbit7 мин. назад

It Took Me a Year to See the Hard Truth About Agent Payments

**Title: It Took Me a Year to See the Hard Truth About Agent Payments** Over the past year, I've worked on infrastructure for the Agent economy, engaging with major players like Stripe, Visa, Coinbase, and numerous startups. The findings reveal a stark reality: genuine, widespread demand for Agent-based payments does not yet exist. **Key Observations:** * **Agent-to-Merchant (Shopping):** The user experience for AI shopping often falls short, especially for visual product discovery. While AI excels at understanding needs, conversational interfaces can't yet replace browsing and comparing multiple products visually. Current merchant interest is largely defensive ("Agent Engine Optimization") for a future that hasn't arrived. High-frequency, low-friction purchases (like food delivery) are potential fits, but lack open APIs and face high AI inference costs. Simpler, more affordable, or cross-language interactions for complex UIs are a niche opportunity but require massive consumer distribution to scale. * **Agent-to-API (Developer Tools):** Developer payment needs for APIs (computing, data, models) are already met through subscriptions and prepaid credits. The core challenge is not payment friction but supplier economics: most large SaaS providers prefer enterprise contracts over micropayments for API calls. Protocols like MPP and x402 suit the long-tail of smaller services but cater to a developer market historically reluctant to pay for these tools. Major infrastructure needs at the top of the stack are already being addressed. * **Agent-to-Agent (Machine Commerce):** This is a long-term vision with almost no current transaction volume. While a future with high-speed, high-frequency, multi-party machine-to-machine transactions would require novel infrastructure, it remains theoretical. The market is not here yet. * **Agent-to-Finance:** This is the only category with clear, present demand. Financial professionals and DeFi users already pay for tools, and AI augmentation is a natural evolution. Autonomous AI agents can enable entirely new financial strategies. However, competition is fierce from established, regulated incumbents who can more easily layer AI onto their existing products. **The Core Insight:** Companies, especially giants with long time horizons, are building defensively for a potential future of mass machine commerce. For them, early investment is a low-cost hedge. For startups, the current market reality is different. The primary challenge isn't just moving money between agents (payments). The larger, unsolved problem is **orchestration** – coordinating work between agents and humans, verifying outcomes, and then settling. Payment is just a part of settlement, which is just a part of orchestration. Companies that solve the orchestration problem will subsume payments, not the other way around. After a year of building, we see the real, growing, and underserved market opportunity lies in this broader domain of orchestration.

链捕手31 мин. назад

It Took Me a Year to See the Hard Truth About Agent Payments

链捕手31 мин. назад

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

A researcher discovered a critical "infinite mint" vulnerability in the Zcash cryptocurrency's Orchard protocol using Claude Opus 4.8, leading to a swift fix but also a 50% market drop, erasing billions in value. This incident highlights a new era where powerful, accessible AI models are dramatically lowering the barrier to finding software vulnerabilities. Previously, the security community feared specialized models like Claude Mythos Preview, capable of finding decades-old zero-day exploits. The Zcash case, however, involved a publicly available, general-purpose model. This shift makes advanced security auditing—and attack capabilities—accessible to far more people, not just experts. The mass democratization of vulnerability discovery brings a dual challenge: a flood of low-quality, AI-generated false reports that overwhelm maintainers, and the real, rapid uncovering of deep, dangerous bugs. Open-source projects, often understaffed and unfunded, are particularly vulnerable to this "attention DDoS." The article cites examples like curl shutting down its bug bounty program due to the unsustainable workload. Our perceived digital safety has often been luck, relying on the high cost and effort required to find deeply hidden flaws in complex systems, as seen with historical vulnerabilities like Heartbleed or Baron Samedit. AI changes this cost structure, effectively "mass-producing flashlights" to illuminate every corner of our codebase. While large companies operate extensive security chains involving external white-hat hackers and massive defensive operations, the global cybersecurity workforce faces a severe shortage, especially of experienced personnel capable of analyzing complex threats and coordinating fixes. The core dilemma emerges: AI makes *finding* bugs cheap and scalable, but *fixing* them remains a slow, expensive, and human-intensive process. The article concludes that AI won't destroy the internet but acts as a bright light, revealing that our digital existence is not inherently secure but is precariously maintained by ongoing human effort. The true cost in the AI era may not be discovery, but whether there will be enough people left willing and able to do the hard work of repair.

marsbit1 ч. назад

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

marsbit1 ч. назад

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit2 ч. назад

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit2 ч. назад

Торговля

Спот
Фьючерсы

Популярные статьи

Manyu: восходящая мем-звезда на Ethereum, готовая открыть новую эру культуры Shiba

Manyu - это мемтокен на Ethereum, который приносит децентрализованную культурную и развлекательную ценность через вирусное влияние в соцсетях и вовлечённость сообщества.

1.9k просмотров всегоОпубликовано 2025.11.27Обновлено 2025.11.27

Manyu: восходящая мем-звезда на Ethereum, готовая открыть новую эру культуры Shiba

Неделя обучения по популярным токенам 14: Glamsterdam — самое ожидаемое обновление Ethereum в 2026 году

Ordinals/Runes по-прежнему стимулируют доходы от комиссий за блоки и активность разработчиков, рассматриваются как отправная точка «нативной эмиссии активов» в сети.

1.5k просмотров всегоОпубликовано 2026.04.29Обновлено 2026.04.29

Неделя обучения по популярным токенам 14: Glamsterdam — самое ожидаемое обновление Ethereum в 2026 году

Обсуждения

Добро пожаловать в Сообщество HTX. Здесь вы сможете быть в курсе последних новостей о развитии платформы и получить доступ к профессиональной аналитической информации о рынке. Мнения пользователей о цене на ETH (ETH) представлены ниже.

活动图片