Unsolicited Tokens Appearing In Your Wallet: Why You Should Not Touch Them
You didn’t go looking for this one
Most crypto scams need you to go somewhere. You click a link, land on a fake claim page, connect a wallet. The unsolicited token turns that around. It comes to you. You open your wallet one morning and there’s a token you’ve never heard of, sometimes with a balance that looks like real money, sometimes with a name that’s a web address and an instruction: visit this site to claim your reward.
The instinct is to do something with it. Sell it, swap it, find out what it is, claim whatever it’s pointing at, or at least send it somewhere so it stops cluttering the list. Every one of those instincts is what the sender is counting on.
This is the core idea of the whole piece, so it’s worth saying plainly at the top. The token sitting in your wallet can’t do anything to you by sitting there. What hurts people is the next step, the one they take because the token made them curious or hopeful. The attack is the interaction.
Farming wallets get more of these than most. They’re active, they touch many contracts, they receive real airdrops, and they tend to be the kind of wallet whose owner is primed to expect free tokens. A wallet that sometimes receives legitimate distributions is exactly where a fake one has the best chance of being believed.
What follows covers why these tokens appear, what the different kinds are built to do, what actually happens if you interact with them, and how to hide them cleanly. It also covers a less obvious cost: what tidying them up across many wallets reveals about which wallets belong together.
Why anyone can put a token in your wallet
A wallet doesn’t hold tokens the way a purse holds coins. On account-based chains, a token is an entry in a contract’s own ledger, a mapping that says this address has this balance. The contract’s owner writes to that ledger. Your wallet reads it.
So “receiving” a token requires nothing from you. Anyone who deploys a token contract can record a balance next to your address, and a transfer event gets emitted that explorers and wallets pick up. Your wallet sees the event, looks up the contract’s name and symbol, and adds a line to your asset list. You didn’t accept it. There’s no accept step on most chains.
Other chains work differently in the details and arrive at the same place. On Solana, tokens live in token accounts associated with your wallet, and someone can create one for you and send tokens into it. NFTs and compressed NFTs can be airdropped to thousands of addresses cheaply. On Bitcoin, anyone can send a tiny output to your address.
This is why “how did they get my address” is the wrong question. Your address is public the moment it transacts. Anyone who reads the chain can find it, and bulk senders pull target lists straight from recent activity, top holder lists or the participants of a well-known protocol. If you’ve interacted with a popular dapp, your address is on a list somebody can scrape.
The design choice that makes this possible also makes legitimate airdrops possible, which is why it’s not going away. A protocol that wants to distribute tokens to past users can simply send them. A spammer uses the same mechanism.
Why a real airdrop season brings more of them
Spam tokens aren’t evenly spread through the year. They cluster around moments when people expect free tokens, and for farmers that’s most of the time.
When a large distribution is announced, attention on that ticker spikes. Recipients are checking wallets daily, searching for the claim page and watching for the token to arrive. A bulk sender who drops a lookalike with the same ticker into the wallets of known protocol users is catching people at the exact moment they’re most likely to believe it. Some recipients genuinely are eligible for the real distribution, which makes the fake easier to accept, because the wallet owner was expecting something with that name.
Points programs and seasons do the same thing on a smaller scale. When a protocol is known to be running points, its users are primed for a token eventually, and a token with the protocol’s name looks like the conversion finally happening. It’s worth knowing ahead of time how the real conversion will be announced, so a surprise token with the right name doesn’t catch you off guard.
There’s also a practical signal in the timing. A real protocol distributing directly to users usually does it once, after an announcement, from a contract it has publicly named. Spam arrives in waves, often from freshly deployed contracts, and often to wallets that have nothing in common except a public interaction with some popular dapp. If a token lands before anything has been announced, the default assumption should be that it’s fake until the project says otherwise.
For a farm, the uncomfortable consequence is that the wallets most likely to receive real tokens are also the ones most likely to receive convincing fakes. There isn’t a filter setting for that. The protection is procedural: every token gets checked against the project’s own announcement before anyone does anything with it.
The shapes these tokens come in
Not all unsolicited tokens are the same, and it helps to recognise the families.
The first is the billboard token. Its name or symbol is a URL, or a sentence like “Claim rewards at” followed by a domain. The token itself is worthless. It exists to put a web address in front of you, inside the one interface you trust, where you’re used to seeing asset names rather than ads. Some wallets now truncate or hide token names that contain links, but plenty still show them.
The second is the lookalike. It borrows the name and ticker of a well-known stablecoin or a token that just launched, and it appears with a balance that looks meaningful. If a real distribution is in the news this week, expect fakes with the same ticker in your wallet within days.
The third is the honeypot. It has a trading pool somewhere with a price, so your wallet might show it as worth something. Buying may work fine. Selling is blocked or taxed to nothing by the contract’s own transfer rules. Its purpose is to lure you into a swap flow, to pull a real asset into the pool, or both.
The fourth is the bait NFT. It usually carries an image with text on it, a voucher or a mystery box that tells you to visit a site to redeem, open or claim.
The fifth is dust, a tiny amount of a real asset. It shows up most often on chains where spending it would link addresses together, which is a privacy attack rather than a theft attempt, and it gets its own section below.
What they share is that they arrived uninvited and they want you to do something.
What actually happens when you follow the link
The billboard and bait NFT families point you at a website. That site is the attack, and it usually runs the same playbook as a fake claim page.
You arrive and it looks official enough: a logo, a countdown, a “check eligibility” button. You connect your wallet. Connecting on its own shares your address, which the site already knew, and not much else. The damage comes with the next prompt.
The site asks you to approve something, sign something, or send something. The approval might be for a real token in your wallet, not the spam one, giving a contract unlimited rights to move it. The signature might be an off-chain permit that grants the same rights without an on-chain approval showing up anywhere until the funds leave. For NFTs it might be a request to approve all of a collection. Or the page might just ask for a “small claim fee” in the chain’s native asset.
These prompts are dressed up. The button says Claim. The wallet popup may show a contract name that looks related to the token. By the time you’re reading the details, you’ve already decided you want the reward, which is the state of mind the page was designed to produce.
The token was only the envelope. It got you to the page, and the page is what drains the wallet. This is why the advice isn’t “check whether the token is real”. You don’t need to. Treat any site the token points to as hostile, because a legitimate project has no reason to announce a distribution by spraying billboard tokens at random wallets.
Why selling or swapping is the trap
Plenty of people who would never click a URL in a token name will still try to sell the token. It shows a value, so it seems silly not to.
Here’s what that involves. To sell a token on a DEX, you usually approve a router to spend it, then call the swap. With a normal token, approving the router for that token exposes only that token. With a spam token, several things can go wrong.
The price may be fake. A wallet’s value estimate often comes from whatever pool exists for that token. Anyone can create a pool with a tiny amount of liquidity and set a ratio that makes the token look valuable. When you try to swap, you’ll find there’s nothing behind the price, or the contract’s transfer rules block the sale.
The token’s own code can be hostile. A token contract decides what happens when its transfer or approve functions run. It can refuse to move for anyone except its deployer. It can charge an enormous tax on the way out. It can emit misleading events. What it can’t do on its own is move your other tokens, since each token contract controls only its own ledger, so the bigger danger is where the swap flow sends you.
And that’s the real risk: the route. If the token isn’t tradable on a mainstream venue, the “sell here” suggestion usually leads to an unfamiliar site or aggregator that prompts approvals for your real assets, or a signature you can’t read. Even on a legitimate DEX, you’re paying gas to interact with a contract written by someone who went out of their way to target you.
The expected value of selling a spam token is roughly zero. The downside isn’t. That arithmetic settles it.
The dust version and what it’s after
Dust works on a different principle, and it’s worth separating out because the risk is privacy rather than theft.
On UTXO chains like Bitcoin, your balance is made of separate unspent outputs. When you spend, your wallet picks some outputs to use as inputs to the transaction. Chain analysis relies heavily on one idea: if several outputs are spent together as inputs to the same transaction, they probably belong to the same owner, since spending each one needs its key.
A dusting attack sends tiny outputs to many addresses. The sender doesn’t expect to steal anything. They wait to see whether you ever spend the dust together with your other outputs. If your wallet sweeps the dust into a transaction along with coins from another of your addresses, you’ve just told anyone watching that those addresses share an owner.
Account-based chains don’t have the same input-merging mechanic, but a related effect exists. If you “clean up” small unsolicited balances by sending them from many wallets to one address, you’ve drawn a line from each wallet to the same destination. That line looks just like the consolidation patterns clustering reviews look for.
The defence for dust on Bitcoin is coin control. Many wallets let you mark specific outputs as do-not-spend, or freeze them, so they never get picked as inputs. For account-based chains, the defence is simply not to move the stuff at all.
What interacting reveals about you
Even when interacting with a spam token doesn’t cost you funds, it tells the sender things.
A transaction from your wallet touching their contract confirms the wallet is active and watched by someone who responds to bait. That’s valuable to them. A wallet that engages once gets targeted more, and with better-crafted lures.
Visiting the site from the token name gives away more than your address. The site sees your IP address, browser fingerprint and timing. If you’ve been careful to run separate wallets in separate browser profiles, opening a scam site from inside a profile connects that profile’s network identity to a party with every incentive to misuse it. If you open the same site from several profiles because several wallets received the same token, you’ve given that party a neat set of sessions to compare.
Connecting a wallet to the site links your address to that session, which the site can log alongside everything else it collected. Signing a message there, even a harmless-looking one, proves control of the key.
None of this is catastrophic on its own. It’s just information you don’t need to hand over, to people you know are hostile, in exchange for nothing.
The consolidation problem for farms
This is where unsolicited tokens become a farming-specific problem rather than a general one.
A farm’s wallets tend to touch the same protocols, so they tend to land on the same spam lists. If a bulk sender targets everyone who used a particular protocol, several of your wallets may receive the same billboard token on the same day. That’s not a link in itself. Thousands of unrelated wallets got it too.
What you do next can create a link. If you go through your wallets and send every copy of the spam token to one address, whether a burn address, your main wallet or some “cleanup” wallet, you’ve made a fan-in: many wallets, one destination, same token, similar timing. That’s a shape chain analysts and later sybil reviews read as common control. You’ve spent gas to publish a map of your own farm.
The same goes for approving and selling the token from every wallet through the same route, or revoking spam approvals in one tight batch session. Each individual action is small. The pattern across wallets is what gets noticed.
The defensive rule is short. Handle unsolicited tokens inside each wallet’s own interface, as a display setting, and never with a transaction that treats your wallets as a group. Hiding a token is local to your app. Moving it is public.
A worked example across ten wallets
Here’s how this plays out in practice, using a made-up but ordinary farm.
Someone runs ten wallets. All ten used the same lending protocol over the past month, at different times and with different amounts. On Tuesday, a bulk sender airdrops a billboard token to every address that interacted with that protocol. Several thousand wallets receive it, including all ten of theirs. The token’s name is a domain, and the symbol says rewards are waiting.
Version one: they ignore it. The token sits in ten wallets, alongside thousands of other recipients. On-chain, the only thing tying their wallets to this event is that they all used a popular protocol, which is true of a huge number of addresses. Nothing new has been revealed. Total cost: nothing.
Version two: they get curious in one wallet. They open the domain in the browser profile that wallet uses, connect, and see a claim page asking for a signature. They get suspicious and close it. They didn’t sign. But the site now has that profile’s IP address, fingerprint and wallet address, plus a record that this wallet belongs to someone who clicks. Probably no funds lost, and a small, permanent piece of information handed to a hostile party.
Version three: they decide to tidy up. Over twenty minutes, they send the spam token from all ten wallets to a burn address, paying gas each time. Now there are ten transfers of the same token from ten wallets to the same destination, in a tight window, which is a pattern that almost none of the other few thousand recipients produced. They’ve spent real money to create a small cluster where there wasn’t one.
Version four: they try to sell it. The wallet shows a value, a swap page says the pool exists, and they approve and swap from the first wallet. The transaction fails because the token blocks sales, or it succeeds for a trivial amount after a huge tax. Either way they’ve approved a hostile contract and paid gas for the lesson.
Only version one costs nothing. It’s also the only one that requires no effort, which is a nice property for a security habit to have.
How to hide them properly
The good news is that the right action is also the cheapest one. Hide the token and move on.
Most wallets have a hide option on each asset. Some have a spam filter that hides tokens from unverified contracts or tokens flagged by a list the wallet maintains or subscribes to. Turn that filter on in every wallet you use. It won’t catch everything, but it removes most of the noise, and hidden tokens stay hidden without any on-chain action.
Explorers help too. Many label suspicious tokens, collapse them under a spam heading, or hide zero-value and flagged transfers by default. When you look at a wallet on an explorer, check whether those toggles are on.
For NFTs, most wallets and marketplaces let you hide items from your gallery. Do that rather than transferring or burning them.
On Solana, there’s a wrinkle worth knowing. Each token account holds a small rent deposit, and closing an empty or burned token account returns that deposit to you. A number of wallets now build this in. Third-party “burn and reclaim” sites also exist, and they’re a common way to get a user to sign something broad. If your wallet has the cleanup built in, use that. Otherwise, hiding is fine. The rent is small, and a stranger’s site asking for signatures isn’t worth it for small change.
What you shouldn’t do is send spam tokens to a burn address or back to the sender. It costs gas, it proves engagement, and across a farm it builds the consolidation pattern above.
When an unsolicited token might be real
Occasionally a token you didn’t request is legitimate. Some protocols distribute directly to past users’ wallets instead of making them claim. So it’s fair to ask how to tell the difference without touching the token.
Start from the project, never the token. If a protocol you actually used announces a direct distribution, the announcement will be on its official site and verified accounts, and it will name the token contract. Compare that official contract address against the one in your wallet. If they match exactly, you have your answer. If the token’s name matches and the contract differs, you’re looking at an impostor, however convincing the ticker. The separate piece on adding a claimed token covers finding and checking the official contract in more detail.
A few features almost never belong to a real distribution. A URL in the token’s name or symbol. A message telling you to visit a site to activate or claim what you’ve already received. A balance of a well-known stablecoin you didn’t buy. A token that shows a large value but has no trading history anyone can point to.
If you can’t confirm it from the project’s own channels, leave it alone. A real token will still be there next week. A fake one will still be a fake. Waiting costs nothing in either case.
The wallet signals worth trusting and the ones that aren’t
Wallets and explorers put a lot of information next to a token. Some of it helps you judge, and some of it is exactly what the sender manipulates.
Mostly trustworthy: the contract address itself, whether the contract is verified on the explorer, how long it has existed, how many holders it has and whether that holder count looks organic, and any spam label an established explorer or wallet has applied. A verified contract from a known project with a long history is one thing. A contract deployed yesterday that sent itself to a hundred thousand wallets is another.
Easy to fake: the name, the symbol, the logo, the displayed price and the displayed dollar value. Names and symbols are free text chosen by the deployer. Logos come from the token’s metadata or a lookup service. Prices come from whatever pool exists, which the sender can create.
Unreliable both ways: the absence of a spam label. Filters work from lists and heuristics, and a fresh campaign may not be flagged yet. A token without a warning isn’t vouched for. It just hasn’t been caught.
When in doubt, trust the contract address and the project’s own announcement, and ignore everything the token says about itself.
What alternatives get wrong
A few common responses make things worse, or at least don’t help.
“Revoke everything after touching it.” Revoking is good hygiene, and if you’ve approved something suspicious, revoke it promptly. But it doesn’t undo a signature you’ve already given, and it can’t recover funds already moved. The better move is not to approve in the first place.
“Use a burner to investigate.” Some people move the spam token to a throwaway wallet to see what the site does. That transfer is itself an on-chain link between your wallet and the burner, and the burner then carries the same bait. If you want to research a scam, look at the contract and the site from a clean environment without connecting any wallet at all.
“Report it and it’ll be removed.” Reporting to your wallet or explorer helps get the token labelled for others, and that’s worth doing. It won’t remove anything from the chain, and it won’t recover anything for people who already interacted.
“Ask in the project Discord whether it’s real.” Asking is reasonable. But posting “I got a token called X, is it legit?” in a public channel is one of the fastest ways to attract the fake support agents who DM new posters with a validation link. If you ask, ask where the answer will come from the project’s own verified announcement, and ignore anyone who replies privately.
“Only big wallets get targeted.” Bulk senders target by activity, not by balance. A farming wallet with modest funds but lots of protocol history is squarely in range, and so is a wallet that received a real airdrop recently.
A routine for a farm with many wallets
Set this up once and it mostly runs itself.
In every wallet app you use, turn on the spam or unverified-token filter and the option that hides NFTs from unknown collections, if there is one. Do it at setup for new wallets, not after the first spam arrives.
Adopt one rule for the whole farm: no transaction ever touches an unsolicited token. No selling, no transferring, no burning through third-party sites, no approvals. The only actions allowed are hiding it in the wallet view and, where your wallet supports it natively, closing empty accounts to reclaim rent.
For any token you think might be a real distribution, verify the contract from the project’s official source before doing anything. Record the official contract address somewhere you keep project notes, so the next wallet that receives it can be checked in seconds.
Keep scam research out of your farming profiles. If you want to see where a billboard token leads, do it from an environment with no wallet connected and no link to your farm’s browser profiles or network setup.
And watch for patterns. A sudden spike of spam into specific wallets after using a particular protocol tells you something about where target lists come from.
Where this advice has limits
I don’t have numbers on how many people lose funds through unsolicited tokens compared with other routes, and I’m wary of any figure that circulates without a method attached. What’s clear from the mechanics is that the token is harmless while it sits there, and the losses happen at the step where someone engages.
Hiding leaves the token exactly where it was: still in your on-chain history and visible on any explorer. If you ever export your history for record keeping, you’ll see the spam there, and you’ll need to separate it from real transfers. Most tracking and accounting tools have their own spam handling for exactly that reason.
The filters themselves aren’t perfect. A spam filter can hide a legitimate token, which is one more reason to confirm real distributions from the project rather than from what shows up in your asset list.
And hiding does nothing about a malicious site you already visited or a signature you already gave. If you’ve interacted, treat it as a possible compromise: check and revoke approvals, move remaining funds from that wallet to one you trust, and don’t reuse the wallet for anything that matters.
For more on wallet security, clean farming habits and the tools we actually use to run many wallets properly, head back to the Airdrop Farming homepage.
Get new guides and videos first — join the Telegram channel.