A single-source flag deserves a shrug until you check the source; real address poisoning deserves a hard look at your own copy-paste habit, and conflating the two turns an honest report into a false accusation.
On November 16, 2026, a founder's screenshot caught Plastron's own wallet report calling a $71,726 transfer "the usual address-poisoning pattern." It wasn't. The address behind it was reported by exactly one community scam list, with no second source, no repeated dust pattern, and no real reason to use the word poisoning at all.
That mix-up matters to anyone reading a wallet screening report and seeing a scary word sitting next to a five-figure number - a compliance reviewer, an OTC desk, or just someone checking a wallet that isn't theirs before accepting a payment. Plastron's scoring engine puts both of these under the same gate, called a materiality gate, because neither one should swing a risk score much on its own. A shared scoring gate is not a shared meaning.
What's the difference between a single-source flag and real address poisoning?
A single-source flag says one list, and only one list, has ever reported this address for anything - no transaction pattern, no second confirmation, nothing beyond a single claim sitting in a community database. Address poisoning is a transaction pattern: someone sends your wallet a tiny or zero-value transfer from an address built to look almost identical to one you already trust, betting you'll copy it straight out of your history the next time you send a real payment.
The first is a data-quality problem. The second is an attack in progress.
Security researchers describe the poisoning mechanism the same way across the board: a lookalike address lands in your transaction history through an unsolicited transfer, and the attacker is betting you check the first and last four characters, not the full string, the next time you copy a recipient. If you want the consumer-side walkthrough of how that trick actually works, see how a lookalike address tricks a copy-paste. A single-source flag has none of that mechanism behind it. It is one unverified claim, full stop.
Both get gated out of the risk score for the same scoring reason, but one is a thin, unverified claim and the other is an active attempt to trick your next transfer.
Head-to-head
Put the two next to each other and the overlap is smaller than the shared gate makes it look. They land in the same bucket of a wallet report for completely different reasons, and only one of them is actually about you doing something wrong.
Criterion
Single-source flag
Address poisoning
What triggers it
One unverified community list names the address, nothing else
A tiny or zero-value transfer lands in your history unsolicited
Scoring treatment
Gated out, shown for context only
Gated out, shown for context only
What it actually tells you
Close to nothing, by itself
Someone is actively targeting your wallet
Real risk to you
Usually none
You could copy the wrong address next time you pay
Right response
Note it, check the source, don't act on it alone
Verify every character before you copy, every time
Plastron's Nov 16, 2026 fix
Now reads "one community list, no second source" - never "poisoning"
Still reads "typical of address poisoning" when the pattern actually matches
The $71,726 transfer almost called poisoning
The address that triggered the fix sent a wallet $71,726 in a single transaction. One community-run scam list, and nobody else, had that address down as a reported phishing contact. Plastron's own brief, before the fix, folded that single claim into language reserved for dust: "small unsolicited transfers ... typical of address poisoning." That sentence was wrong on every count. One transaction isn't a pattern. $71,726 isn't dust. And one unconfirmed source isn't the same evidence as a repeated, labeled attack.
The fix tells the two apart by what the underlying evidence actually says. A flag downgraded because it looks like dust still reads as "typical of address poisoning." A flag downgraded because exactly one list reported it now reads "one community list reports this, with no second source" - wording that hands the reader a fact to weigh instead of a label the data never earned.
A single $71,726 transfer from a single-source address was misread as address poisoning until the November 16, 2026 fix separated the two meanings for good.
Does a single-source flag mean your wallet is clean?
No, and that's the nuance most wallet reports skip. A single-source flag is weak evidence, not an all-clear, and weak evidence still deserves a second look rather than a shrug.
There's one case where a single-source flag earns more weight than the rest of this post gives it: when the one source is a government list rather than a crowd-sourced one. An OFAC designation, a FinCEN alert, a court filing - a single source there is already authoritative, and the "only one list" logic that downgrades a crowd-sourced claim doesn't apply the same way. A lone community report and a lone government designation aren't the same thing just because both technically come from one list.
The same honesty cuts the other way for poisoning-shaped dust. A zero-value transfer sitting in your history is real evidence someone is targeting you, not proof you already lost anything - and skipping it entirely is the wrong instinct too, which is why leaving dust untouched is still the right move rather than interacting with it. Nobody emptied your wallet because a $0.00 transfer showed up. The actual danger only arrives the moment you copy a recipient address without checking every character - a habit fix, not a wallet problem.
You can run the single-source cross-check by hand today: pull the address up on a community scam-report site like Chainabuse and see whether any other list backs up the same claim. Screen the wallet with Plastron instead and that single-source label is already there, with the dust gate and the poisoning gate kept apart, in one read.
Verdict
Read a single-source flag as a tip, not a verdict - check what the one source actually is before deciding how much it matters. Read address poisoning as a live warning about your own copy-paste habit, not a sign your wallet got drained. The $71,726 case is the cleanest argument for keeping the two apart: the only thing wrong with that wallet was the label Plastron put on it, and fixing the risk score's label mattered more than fixing anything on-chain.
FAQ
Is a single-source flag a false positive?
Not exactly. A false positive is a flag that was wrong altogether. A single-source flag can be completely true and still barely worth weighing, because one list reporting something is thinner evidence than two or three lists agreeing on it.
Does address poisoning always use a tiny dust transfer?
No. Zero-value and counterfeit-token transfers make up most of it today, not plain dust. Any transfer that plants a lookalike address in your history counts, regardless of the dollar amount behind it.
What should I do if my own wallet shows a single-source flag?
Check what the one source actually is before reacting to it. A report from a government list or a named law-enforcement source carries far more weight alone than a single crowd-sourced scam-tracker entry does.
Why does a wallet report still show a flag it isn't scoring?
Context. An exchange reviewer or counterparty might ask about that address later, and a report would rather show it, labeled honestly, than leave a gap the next question fills with guesswork.
Disclaimer: This article is for educational and informational purposes only and is not legal, financial, tax, or compliance advice. Crypto carries risk; you act on this information at your own risk. Always do your own research and consult a qualified professional before making decisions. Views are the author's own and do not constitute financial, legal, or investment advice.
About Plastron
Plastron is a free, non-custodial wallet screening tool. It checks Ethereum and six EVM chains for AML and KYT risk — sanctions exposure, mixer contact, and stolen-funds proximity — and returns a risk report in seconds. It reads public on-chain data only: it never takes custody of funds and never asks for private keys.