Android

27940 readers

102 users here now

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:

[email protected]

founded 1 year ago

MODERATORS

[email protected]

126

Android malware steals payment card data using previously unseen technique (arstechnica.com)

submitted 2 months ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

Attacker then emulates the card and makes withdrawals or payments from victim's account.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 months ago (1 children)

There is nothing being subverted, nfc has applications other than contactless payments that require it acting as the reader, which is why it's supported. It would be better if it was behind an explicit permission (just like other sensors would) but limiting it to only responding to readers is like limiting Bluetooth to audio transmission.

[–] [email protected] 1 points 2 months ago (1 children)

This isn't about subscribing to NFC events, the malware is creating fake NFC events without the NFC sensor being involved in a physical interaction with a tag or reader.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (1 children)

No? The nfc sensor is next to the credit card, which is why it's able to communicate with it to relay it.

Why would it need to create fake events? How would that even help?

[–] [email protected] 0 points 2 months ago (1 children)

There's no credit card involved in this scenario.

The attacker uses phone A and touches the ATM NFC reader. This creates a NFC event on phone A that requests a token.
Phone A sensds the request data to the malware running on victim's Phone V.
The malware on phone V creates a fake NFC event that makes it look like the phone V was touched against the ATM. <-- this is the huge security issue IMO
The app on phone V that's currently associated with NFC contactless payments responds to the fake NFC event by issuing a token.
The malware on Phone V sends the token to phone A.
Phone A uses the token to "prove" to the ATM that the real customer is in front of it.
The ATM asks for the PIN and the attacker supplies the correct PIN (which they've previously obtained via social engineering).
Attacker can now withdraw cash from the ATM from the victim's account.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (1 children)

What scenario are you talking about?? From the article:

NGate malware can relay NFC data from a victim’s card through a compromised device to an attacker’s smartphone, which is then able to emulate the card and withdraw money from an ATM.
...
Masquerading as a legitimate app for a target’s bank, NGate prompts the user to enter the banking client ID, date of birth, and the PIN code corresponding to the card. The app goes on to ask the user to turn on NFC and to scan the card.

Physical card is involved, mobile payments isn't.

[–] [email protected] 1 points 2 months ago

In that case I call bullshit. What I described can work (relaying banking apps on the victim's phone to authenticate to ATM), with cards it should not. If you read the comments on the site you'll see people are just as confused as to how this can work.