Glossary

    Glossary

    Dusting Attack

    A dusting attack sends tiny amounts of crypto to thousands of wallets to link addresses to real identities through spending patterns and exchange KYC. The dust is bait, not a gift - moving it, or merging it with your funds, is how the tracking works.

    SecurityLast reviewed 2026-10-01

    What it is

    Dusting is an attack that sends tiny amounts of cryptocurrency - often fractions of a cent - to thousands of wallet addresses at once. The attacker is not trying to take anything; the dust is bait. The goal is to link wallets to each other and to real identities: when a recipient spends the dust together with their own coins, the transaction publishes on-chain that the same person controls both. Combine that cluster with the identity an exchange collected at sign-up, and an anonymous wallet becomes a name.

    The attack is passive, which is what makes it easy to ignore and easy to survive. The dust sits in the wallet costing nothing, and the entire attack depends on the recipient doing something with it. A variant pairs the dust with address poisoning - bait transactions crafted from lookalike addresses so a later copy-paste grabs the wrong one - and the address-poisoning entry covers that version. For Australian readers, the KYC layer is the reason this works: every AUSTRAC-registered exchange has verified your identity, so a linked cluster is one deposit away from a real name.

    Key takeaways

    • A dusting attack sprays tiny amounts of crypto to thousands of wallets to map who owns what.
    • The dust is bait: spending or merging it lets chain analysis cluster your addresses together.
    • Once a cluster links to an exchange account, KYC turns a wallet into a real name.
    • It is not theft - the dust sits in your wallet and costs nothing to ignore.
    • Address poisoning is the adjacent scam: bait transactions crafted to look like your real history.

    How it works

    The mechanics run on the UTXO model. An attacker scripts thousands of dust transfers - a few hundred satoshis each, well under a dollar AUD - and broadcasts them to addresses scraped from the chain. Each recipient now holds a dust output. The hope is that a wallet or a person consolidates it: spend the dust along with a real output, and the transaction consumes both inputs at once, publishing to the entire network that whoever controls the real coins also received the dust.

    From there the attack has two uses. Chain analysis firms cluster addresses by shared transactions, and a cluster that ever touches an exchange deposit becomes an identity through the exchange's KYC records. Or the dust is a spearhead for targeted phishing: extortion emails quoting an 'unknown wallet' balance, tailored scam messages, or follow-ups that look more credible because they arrived after the dust did. The defence is one behaviour: do not move unsolicited tokens. Ignore the dust, and the cluster never forms.

    For Australian readers, the KYC half is not optional - identity verification is a legal requirement on every AUSTRAC-registered exchange, which the KYC entry covers. That is why the chain-analysis step matters more here than the dust itself: the dust is cheap, the identity link is the prize.

    Why it matters

    Dusting is a privacy attack, not a theft, and the distinction matters for how you respond. Nothing is taken, no signature is requested, and no funds are at risk - which is why the correct response is inaction, not a cleanup. The dust cannot spend itself.

    A colleague named Brent (yes, that Brent) received a dusting spray, found it untidy, and swept every 'stuck' balance into one transaction to clean up his wallet - merging the attacker's dust with his own outputs and publishing the exact cluster the attacker wanted. Nothing was stolen from him, but his wallets were linked from that day, and the extortion email he received months later quoted a balance that only chain analysis could have assembled.

    The highest-leverage habit is to treat unsolicited tokens as radioactive: ignore them, label them, and never merge them with real funds. Report extortion emails to Scamwatch and ReportCyber rather than replying, and check any address copied from history against the address-poisoning entry's middle-characters habit.

    Real-world examples

    The dust that arrived overnight

    A wallet receives a transfer of 546 satoshis - under a dollar AUD at Bitcoin's recent $118,203 - from an address with no history. The amount is too small to spend usefully and too small to be a mistake. It sits in the wallet as a UTXO, and the correct response is no response: do not move it, do not merge it, and label the address in your wallet's notes as unsolicited. The dust costs nothing to ignore and everything to touch.

    How a cluster becomes a name

    A recipient spends the dust together with 0.5 bitcoin from another address - the transaction consumes both inputs, linking the two on-chain permanently. Chain analysis clusters the linked addresses, and months later one of them deposits to an AUSTRAC-registered exchange, where identity verification ties the cluster to a name and date of birth. The chain of custody is complete: dust, cluster, KYC, identity. Every step was public except the last, which is why the exchange step is the one to think about.

    Dusting versus address poisoning

    A related attack sends dust from a lookalike address - same first and last characters as an address you have used - so the transaction appears in your history. Weeks later you copy that address from your history to receive a payment, and the middle characters differ by two. The address-poisoning entry covers the check: verify the first and last characters plus the middle on every paste. Dusting sprays bait tokens; poisoning plants bait addresses.

    Common mistakes

    Mistake: Spending unsolicited dust to clean up the wallet.

    Why it bites you: Merging the dust with real outputs publishes the exact cluster the attacker wants. Brent's cleanup sweep linked his wallets from that day forward.

    Mistake: Assuming the dust is a gift or an accident.

    Why it bites you: Spraying thousands of transfers costs the attacker real fees, which is the motive made visible. Nobody pays to give away fractions of a cent.

    Mistake: Replying to extortion emails that quote your balance.

    Why it bites you: Engagement confirms a live target and escalates the contact. Report to Scamwatch and ReportCyber instead - the paper trail starts there.

    Mistake: Copying a receive address from transaction history.

    Why it bites you: That is address poisoning's trap rather than dusting's, and the lookalike bait sits in history waiting. Verify first and last characters and the middle before every paste.

    Ivy's take

    I read two chain-analysis papers so you don't have to, and the economics settled the question before the cryptography did. An attacker pays real fees to spray dust worth fractions of a cent, so the dust is never the product - the identity is. The whole attack is a chain from bait to cluster to KYC, and it breaks at the first step you control.

    The recurring Brent conversation is his cleanup sweep, which combined every mistake in one transaction and would have been free to skip. My position: unsolicited anything is not yours to manage - ignore the dust, report the emails, and never merge what you did not send. Privacy in crypto is mostly the absence of actions, which is a rare bargain: the cheapest defence in this glossary is doing nothing.

    Related jargon, defined

    Dust
    Amounts so small that spending them costs more in fees than they are worth.
    Address poisoning
    Bait transactions from lookalike addresses planted in your history.
    Chain analysis
    Clustering addresses by shared transactions to link wallets together.
    KYC
    The identity verification every AUSTRAC-registered exchange must run.
    Cluster
    A set of addresses chain analysis attributes to one owner.
    UTXO
    An unspent output; the input a transaction consumes when you spend.

    Frequently asked questions

    Can a dusting attack steal my crypto?+

    No. Dusting sends tokens to you and cannot take anything - spending requires your signature. The attack is a privacy attempt, not a theft.

    What should I do if I receive dust?+

    Nothing. Leave it unspent, label the address as unsolicited, and never merge it with your own funds in a transaction. The dust cannot spend itself.

    Why do attackers bother with tiny amounts?+

    The dust is bait for a chain-analysis cluster, and a cluster that touches an exchange becomes an identity through KYC records. The identity is the prize; the dust is the cost of casting.

    Is receiving dust a security risk on its own?+

    Not by itself. The risk is your later behaviour - spending it, merging it, or responding to phishing that references it. Inaction is the entire defence.

    How is dusting different from address poisoning?+

    Dusting sprays bait tokens to cluster wallets; poisoning plants bait addresses in your history so a future copy-paste misses. Both are countered by the same habits: ignore unsolicited transfers and verify addresses character by character.

    Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

    Keep learning

    Ivy Sinclair-Wren

    Ivy Sinclair-Wren

    Financial Chaos Analyst

    Connect on LinkedIn

    Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.