Join our Newsletter — 33% off our NHI Course

How did Address Poisoning reach industrial scale?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Industrialised address poisoning has reached 65.4 million transactions since January 2025, with about 316,000 confirmed attacks and a Safe{Wallet} campaign that created roughly 15,000 malicious proxy addresses, according to Blockaid. Recipient checks can no longer rely on wallet history alone when the display layer itself can be manipulated.

Editorial analysis by NHI Mgmt Group, based on content published by Blockaid: “Address Poisoning: The Growing Threat Draining Millions from Crypto Users”.

By the numbers:

  • Since January 2025, Blockaid has flagged over 65.4 million address poisoning transactions on-chain.
  • Blockaid reports January 2026 poisoning attempts rose from 628,000 in November 2025 to 3.4 million in January 2026.

Key questions

Q: Why do lookalike blockchain addresses create such a high fraud risk?

A: Because human verification is weak against long hexadecimal strings.

Q: What are the signs that a wallet workflow is being poisoned?

A: Common signs include unfamiliar addresses appearing in history, unexpected nested accounts or contacts in the UI, repeated dust transfers from unknown sources, and recipients that closely mirror known destinations.

Q: What fails when users rely on wallet transaction history to verify recipients?

A: The failure is a broken trust model.

Practitioner guidance

  • Eliminate transaction-history recipient selection Require users to pull recipients from a verified address book, bookmarked source, or separate confirmation channel instead of copying from recent wallet activity.
  • Harden wallet UI trust boundaries Review any feature that inserts external objects into the wallet view, including nested accounts, address suggestions, and recent-contact lists, and flag them as untrusted until explicitly verified.
  • Verify full address match, not partial prefixes Train users to compare the complete recipient string, including the middle characters, because attackers deliberately mirror the parts most people check.

Bottom line: Address poisoning exploits human verification shortcuts and wallet UI trust, not a protocol flaw.

Glossary terms: Address Poisoning, Vanity Address Generation, Device Trust Boundary, Dusting Transaction

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Address poisoning has become an identity-verification failure, not just a crypto fraud tactic. The core weakness is that users are forced to treat partial address recognition and recent history as proof of legitimacy. That is a trust problem, not a protocol problem, and it means any environment that relies on human confirmation of machine-generated identifiers is exposed to the same pattern. The practitioner conclusion is simple: if the identifier is too hard to verify manually, the workflow is already outside safe trust bounds.

A few things that frame the scale:

  • 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
  • Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.

A question worth separating out:

Q: Should organisations require a separate confirmation step for large crypto transfers?

A: Yes, if the workflow depends on human-selected addresses. A separate confirmation step is a compensating control for identity-by-appearance problems, especially when the same interface can be manipulated by dusting or nested object injection. The second channel should confirm the exact recipient and not just the amount, otherwise the attacker can still win on trust.

👉 Read our full editorial: Address poisoning is scaling through automation and supply chain tooling


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.