Blog
Can a stranger steal from your card by tapping it in a crowd? Myths tested
Claims about ghost tapping and contactless skimming tested against how tap payments work, separating the malware relay scam from the crowd-scanning story.
The story goes like this: a thief walks through a crowded train carriage with a payment terminal in a backpack, brushes past dozens of pockets and collects money from every contactless card within reach. It is a vivid picture and it has spread widely online. The sources gathered for this site do not support the crowd-scanning version. What they do support is a different scam with a similar name: "ghost tapping", which works through malware on a victim's phone, usually after the victim is tricked into installing an app. This article tests eight common claims one at a time, says what is true, what is half true and what is false, and ends with what to do. It is about how tap payments work, not a promise that nothing can go wrong.
First, what a tap actually sends
To judge any claim, it helps to know what happens when a contactless card touches a terminal. A contactless card, marked with the contactless symbol, contains a chip and a small antenna. The antenna is powered by the terminal's field, which only works at very short range, a few centimeters. The terminal and the chip exchange a short conversation. The chip sends the information needed to process the payment and produces a one-time cryptographic code for that specific transaction. The issuer checks the code. A copy of last week's code is useless, because each one is made for a single purchase.
What the exchange does not include is the three-digit security code printed on the back, which is used for online purchases and is not part of the tap. The EMV chip standard is the same one used when you insert the card, and tapping is the same conversation carried over a short-range radio link. contactless payment is a convenience layer on a system built to resist copying. That is why the first claims below fail.
Myth 1: "A thief with a reader can drain my card as he walks past"
Verdict: not supported. The antenna in a card has no battery. It works only when a reader's field is very close, a few centimeters, so a thief would have to bring a device right up to your pocket, and doing it to many people in a crowd would be conspicuous. More important, even if a reader did pick up information from a card, the data on its own does not allow a thief to create a new card-present payment. A terminal-based purchase needs the one-time code generated for that transaction, and the code is made by the chip when the terminal asks for it.
A caution about precision. Some information on a contactless card, such as the card number and expiry date, can in principle be read by a close-range reader. That is not nothing, since a card number can be misused in some online settings, though most online merchants and issuers ask for more than the number, including the security code on the back and, increasingly, a one-time code. The sources used for this site do not document crowd-scanning thieves, so the claim as told is an urban legend, not a known pattern. If a card number is misused by any method, the same protection applies: federal law caps a cardholder's liability for unauthorized use at $50, and if only the account number was stolen the CFPB says the cardholder generally has no liability for unauthorized use.
Myth 2: "Ghost tapping means strangers tap your card without you knowing"
Verdict: false as stated, and the real thing is worse in a different way. The phrase "ghost tapping" has attached itself to the crowd-scanning story, and it is a different scam. According to security researchers writing in 2025, ghost tapping works through malware: a victim's Android phone is made to read card data with a reader app, and a criminal's "tapper" app on another device replays that data at a terminal. In reported cases the victim is first tricked, often by a message or a call that pretends to be a bank, into installing an app and doing something with the card.
Group-IB, a security firm, reported tracking at least $355,000 in illicit transactions from one point-of-sale vendor between November 2024 and August 2025, and more than 54 malware variants. Those numbers come from one firm's research as reported in security press, not from a count of all cases. The point is not the total. The point is the mechanism. The criminal does not need to be near you. He needs you to install something, and the chain begins with a lie, not with a crowd.
That changes what a useful defense looks like. A wallet that blocks radio signals does nothing against a scam that begins with you installing an app. The defense is in not installing apps or following instructions from someone who contacted you, and that links directly to the caller says they are my bank's fraud department: three scenarios.
Myth 3: "An RFID-blocking wallet or sleeve is necessary"
Verdict: unsupported as a necessity, harmless as a choice. Because the crowd-scanning scenario is not documented in the sources, a blocking sleeve addresses a risk that is not shown. It does not hurt anything, and some people like the peace of mind. It does not address the risks that are documented: a lost card, a stolen card, a number taken from a merchant, a phishing page and a malware relay. If you are deciding where to put attention and money, the documented risks are the ones to cover first.
Myth 4: "Tapping is less secure than inserting the chip"
Verdict: mostly false, with one caveat. The tap and the insert use the same chip standard, and each produces a one-time code. The big security improvement was the move from the magnetic stripe, whose static data could be copied, to chip transactions. Visa says EMV cuts counterfeit card fraud by more than 80 percent compared with the magnetic stripe, a figure from the network's own material. In the United States the liability for counterfeit card-present fraud moved in October 2015 to the party that had not adopted chip (with gas pumps delayed until April 2021), which pushed merchants to install chip terminals.
The caveat concerns a lost or stolen card. A card that can be tapped can be used by whoever holds it for small purchases without a PIN, depending on the terminal and the issuer's settings. The remedy is the usual one: report a lost card at once. If a card is reported lost before it is used, there is no liability, and the cap otherwise is $50. tap, chip, swipe or phone wallet: how each protects your card data sets all four ways to pay side by side.
Myth 5: "Paying with my phone is riskier than the card"
Verdict: the reverse is generally true. A phone wallet does not send the real card number to the merchant. It sends a device-specific stand-in, called a token, along with a one-time code, and the merchant never sees the number. This is tokenization. A merchant that is breached later holds a token that is of little use elsewhere. Unlocking the phone with a face, fingerprint or passcode is also a step that a plastic card lacks.
The phone has its own risks. A lost phone with a weak lock, malware on the device and a fake "verification" call that persuades you to add your card to a criminal's wallet are the realistic ones. I lost my phone and my cards are in its wallet. What do I do first? covers the lost-phone case.
Myth 6: "If fraud happens by tapping, I am stuck with the loss"
Verdict: false. An unauthorized charge on a credit card is treated the same way whether the number was used by tapping, by typing or by swiping. Federal law caps a cardholder's liability at $50, the issuer carries the burden of proving the conditions for even that amount, and reporting a lost or stolen card before use means no liability. A written billing-error notice must reach the issuer within 60 days of the statement that shows the charge to preserve the statutory rights, and many issuers also run a zero-liability policy that goes beyond the legal cap. A phone call alone may not trigger the statutory protections, but many issuers accept disputes by phone as a courtesy.
The exception is when you made or approved the payment yourself, including after being tricked. That case is judged on its facts, as scam payment or unauthorized charge: why your protections can differ describes. Debit cards and bank accounts have different rules, so ask your bank about them.
Myth 7: "Contactless fraud is everywhere"
Verdict: unsupported by the sources used here. The fact sheet behind this article did not find a reliable count of contactless fraud. A widely repeated industry figure of about $14 billion in annual U.S. card fraud losses traces to a low-quality source and is not used here. What the Federal Reserve's risk-officer surveys report is that credit card fraud was about 5 percent of surveyed institutions' payments-fraud losses in a 2024 survey, while debit card fraud was 39 to 40 percent in two surveys. That is a share of surveyed institutions' losses, not a fraud rate, and it does not separate tapping from other methods. The honest statement is that card fraud exists, that most of the documented patterns are not about strangers scanning pockets, and that precise tap-specific figures are not available.
Myth 8: "I can tell when someone is scamming me this way"
Verdict: not reliably. A ghost-tap scam starts with a message or call that looks like a bank. It asks you to do an ordinary-seeming thing: install an app for "security", hold your card to your phone to "verify" it, or enter your PIN. Each step is small, and the story is consistent. The only dependable defense is the checklist in the next section: do not act on instructions from someone who contacted you.
What a relay attempt can look like
This is a labeled hypothetical assembled from the pattern the security researchers describe, not a record of a real case. Say Alma receives a text that appears to come from her card issuer: her card has been flagged, and she must install a security app and call a number within the hour. A friendly person answers and says the app will "confirm" the card. The app asks for unusual permissions. Then she is told to hold her card to the back of her phone and enter her PIN, which the app says is needed to finish verification.
On her side nothing dramatic happens, perhaps a screen that says "verified". On the other side, the card data the app collected is relayed to a criminal's device, which presents it at a terminal somewhere else, possibly during the same hour. Alma's first sign is an alert or a statement line from a place she has never been.
Every step in that story began with a contact she did not start. None of it depended on anyone standing near her. What stops it is the habit from the checklist below: a real issuer does not ask you to install an app or tap your card to your phone because of a text or a call you did not request. If Alma had hung up and called the number on the back of her card, the representative would have told her there was no such flag. If she had already done it, the steps are in I clicked a phishing link and typed in my card number. What now?: call the number on the card, remove the app, change passwords from a different device and check the statements.
A short checklist that matches the real risks
Work down this list once, then stop worrying about pockets.
- Do not install an app, or follow instructions about your card and phone, because someone contacted you. This is the lesson of the one documented scheme. If a caller or message says your card needs to be tapped to your phone to be "verified", hang up and call the number on the back of the card.
- Install apps only from your phone's official store, and be wary of apps that ask for accessibility or device-control permissions that a payment or banking app has no need for.
- Lock your phone with a passcode, face or fingerprint, and keep the wallet's own locks on.
- Report a lost card or phone immediately. The number on the back of the card is the way to do it. The can someone steal from your card by tapping it through your pocket? article takes the same question from the angle of a pocket and a bag.
- Turn on transaction alerts so that every tap generates a notice. An alert is the quickest way to notice a charge you did not make.
- Look at your statements. A tap does not add a new kind of line item, but it does make small charges easier to overlook. Check them.
- Use a physical blocking sleeve only if it gives you peace of mind, knowing that it addresses a risk the sources do not document.
If you did install an app or follow a call, treat it as an emergency: disconnect from the internet, remove the app, change passwords from another device, and call the number on the back of the card. If an issuer does not help, the CFPB takes complaints at its website.
Key takeaways
- A tap sends a one-time code made for that single transaction, over a range of a few centimeters. Replaying an old tap does not work, and the sources used here do not document crowd-scanning thieves.
- "Ghost tapping" is a malware relay scam: the victim is tricked into installing an app, and a criminal's device replays the card data. Group-IB reported at least $355,000 in illicit transactions from one vendor between November 2024 and August 2025.
- Tap and chip use the same standard, and a phone wallet sends a token, not the real number. Each is generally safer than a swipe.
- Unauthorized use on a credit card carries a $50 federal liability cap however it happened. A payment you were tricked into approving is judged on its facts.
- The defense that fits the documented risk is behavioral: do not install apps or follow card instructions from anyone who contacted you, and report loss quickly.