Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
For those confused about how this could work with chip cards, the malware has two components, one installed on the victims phone and one on the attacker's. The attacker initiates the contactless authentication at an ATM or contactless payment and their phone communicates in real time with the victim's, which is tricked by the malware into reacting to that event and producing the one time token which is then relayed to the attacker and used.
They also previously social-engineered the card PIN from the victim, in case the contactless event requires it (definitely in case of ATM login).
The fact you can trick the NFC system on the phone into reacting to "phantom" payment events and intercept the resulting token sounds like a pretty big problem. The former should be entirely hardware controlled, and the latter should not allow the token to go anywhere else except to the hardware.
That's not what's happening though? It's relaying a physical card's nfc not tricking mobile contactless payments
That's what I mean, it shouldn't be possible to relay anything. It should only trigger when there's a reader physically in proximity to the phone.
Please keep in mind this is happening on the victim's phone which is not rooted, the malware is a regular non-system app.
If it were happening on a rooted phone I could understand being able to subvert the NFC chain because at some point it has to pass from hardware to software and if you're privileged enough you can cut in there. But the malware app is not privileged.
android permissions arent meant to be bypassable either but i bet theres malware that does it. its kinda what it does.
When it happens it's a security flaw and it needs to get patched. It's not normal everyday thing.
exactly! thats what i mean.