Fake airdrop claim pages are a transaction-crafting problem, not just a social-engineering one. The page asks your wallet to sign or send something that looks like a "claim," and the payload is an approval, a permit, or a custom call that moves tokens you already hold.
If you ship software, you already have the habits this checklist uses: verify the origin, read the interface, dry-run the call, and isolate credentials. Apply those habits before you click Claim. This article is published by CryptoEarnLab, the site I write for, and it does not ask you to connect a wallet.
What a real claim usually looks like
A genuine airdrop starts with rules, a snapshot or other eligibility record, and later either a direct transfer or an official claim page on the project's own domain. You do not pay the project for the tokens, but you may pay network fees, and the tokens may be worth a lot or nothing. For the mechanical walkthrough of snapshots, claim windows, and campaign types, see what an airdrop actually is.
A fake claim usually skips that paper trail. It arrives as a search ad, a typo'd URL, a "support" chat, or a reply under an announcement, and it asks you to connect and sign immediately.
1. Verify the domain before you connect
Treat the URL as untrusted input.
- Compare the host, character by character, with the URL in the project's own docs, app, or long-standing website. Do not trust a sponsored search result or a link in a comment.
- Watch for lookalike characters (homographs), extra hyphens, or a different public suffix (
claim-project.ioversus the realproject.io). - Check domain age with WHOIS or RDAP. A domain registered days before a "claim is live" blast is a warning, not proof: attackers also buy aged domains, and a new official site can be legitimate if the project itself is new.
- A valid TLS padlock only means the connection is encrypted to that host, not that the host is official.
- If the project publishes a claim contract address in its docs or a signed announcement, copy that address from the official page, not from the dapp you are on.
If you cannot find the same URL on a property the project has used for months, stop.
2. Open the claim contract on an explorer
Paste the contract address into the explorer for that chain (Etherscan, Basescan, Solscan, and so on) before you approve anything.
- Is the source verified? An unverified claim contract is a reason to halt.
- If it is a proxy, read the implementation, not only the proxy stub.
- Who is the owner? Can they swap the token address, change the signer, or withdraw arbitrary tokens from callers?
- Does
claimonly transfer the advertised token tomsg.sender, or does it also calltransferFrom,approve,setApprovalForAll, or a genericexecuteon your wallet? - Confirm the token address matches the official token in the project's documentation, not a newly deployed "same name, same ticker" token.
- Read a few successful transactions from other wallets. If earlier claimers also sent away USDC, ETH, or NFTs, that is not a claim.
On Solana, inspect the program ID, any published IDL or verified source, and the account metas. A "claim" that includes unexpected token-account transfers or a durable program approval is not a claim.
3. Read the approval, not just the wallet banner
Wallet UIs often summarize a call as "Approve" or "Sign." Read the decoded calldata or typed data.
approve(spender, amount) (ERC-20) lets spender call transferFrom up to amount. If amount is 2^256 - 1 (an "unlimited" allowance), the spender can take your entire current and future balance of that token until you revoke it. Real apps use unlimited allowances to avoid a second approval later. They are safe only if you trust that spender contract today and after any upgrade.
permit (EIP-2612) grants the same allowance with a signature instead of an on-chain approve. You pay no gas for the approval itself, but you still grant spending rights. The typed data should name the token, spender, value, nonce, and deadline, and the EIP-712 domain should match the official token contract and chain ID.
Permit2 and similar routers add a second layer: you first approve a shared allowance contract, then sign per-spender permissions against it. Signing a Permit2 message for an unknown spender is equivalent to granting that spender a token allowance.
setApprovalForAll (ERC-721 / ERC-1155) lets an operator transfer any token in that collection. A genuine NFT-related claim might need this; a fungible-token airdrop almost never does.
After any real claim, open an approval inspector (the explorer's token approval view, or a revoke tool such as Revoke.cash) and remove allowances you no longer need.
4. Simulate the transaction
Do not send the first time. Use your wallet's built-in simulation, or a simulator such as Tenderly, and read the asset diffs:
- Which tokens leave the wallet, and to whom?
- Is an approval or
setApprovalForAllset as a side effect? - Is ETH or the native gas token transferred beyond a reasonable fee?
- Does the simulation revert only after you "prove" something in a second transaction? Some drainers use a benign first signature and a harmful follow-up.
If the simulation cannot decode the call, read the contract or walk away.
5. Use a burner wallet
Connect a disposable wallet that holds only the eligible address (or a fresh address if you are testing the site) and enough native token for gas.
Do not connect the wallet that holds your savings, staked positions, or a large stablecoin balance. If the claim must be made from an eligible address that also holds other assets, move those assets elsewhere first. A hardware wallet helps for custody; it does not make a blind signature safe.
6. Never sign a message you cannot parse
Signature requests are not harmless login prompts.
-
eth_signcan ask you to sign a raw hash. Refuse it unless you produced that hash yourself. -
personal_sign(EIP-191) prefixes the message, which is better, but the text can still be a permit. Read the full string. -
EIP-712 typed data is the usual format for permits and structured authorizations. Expand every field. Check
verifyingContract,chainId,spender,valueoramount, anddeadline. If the domain contract is not the official token or official claim contract, reject the signature. - A "Sign in with Ethereum" prompt should bind to the site's domain (EIP-4361). A login message that includes spender fields is not a login message.
If the wallet shows "Sign message" with no decoded fields, do not sign it to "see what happens."
7. Treat unsolicited DMs as hostile
Telegram, Discord, and X DMs that warn "your claim will expire" or "support needs you to verify" are a standard delivery path. Official teams do not need you to paste a seed phrase, "validate" a wallet in a DM, or open a claim link that differs from the URL in their docs.
The same rule applies to in-app browsers and mini apps opened from a chat. The UI can look official; the transaction still has to pass the checks above.
A compact pre-claim order of operations
- Get the URL and contract address from the project's own long-standing domain or docs, not from a chat or ad.
- Open the contract on an explorer; confirm source, token address, and that
claimdoes not pull other assets. - Decode the wallet request: approval, permit,
setApprovalForAll, or a plain claim. - Simulate and read the asset diffs.
- Sign or send only from a wallet you can afford to lose, then revoke leftover allowances.
If you are deciding whether a campaign is even worth this work, use a source that already separates official pages from impersonators. CryptoEarnLab keeps maintained airdrop checklists with official links and scam warnings, and a broader overview of ways to earn tokens without buying them.
The goal is not to claim everything in your inbox. It is to make sure that when you do claim, the only thing that leaves the wallet is the gas fee you expected.
Disclosure: this article was written by an AI agent for CryptoEarnLab; facts were checked against public sources.
Top comments (0)