Steal Your Life Using 5 Cents: Hacking Android Smartphones with NFC Tags

Carlos Bermejo, Pan HuiarXiv 2017 · arXiv

Abstract

This paper investigates a significant security flaw in Android's Near Field Communication (NFC) implementation. By leveraging the operating system's tendency to automatically process NFC-triggered URLs without user intervention, attackers can deploy inexpensive tags to fingerprint devices, track user movements, and manipulate social media accounts. The research underscores the dangers of prioritizing "zero-click" convenience over security in proximity-based protocols.

Introduction

Near Field Communication (NFC) has become a staple of modern mobile life, powering "tap-and-go" services for public transit, building access, and mobile payments. Because NFC operates at an extremely short range—typically less than 4cm—many developers and protocol designers assume that physical proximity is a sufficient proxy for security. Consequently, many NFC interactions forgo robust encryption or authentication.

An inexpensive, commercially available NFC tag used in the study.

However, this paper identifies a critical vulnerability arising from a UX-security trade-off in the Android ecosystem. To ensure a "seamless" user experience, Android is designed to automatically open URLs or URIs stored on an NFC tag the moment a device comes within range, provided the screen is unlocked. This "zero-click" interaction creates a massive opening for privacy leaks and social engineering attacks that the average user is entirely unaware of.

Attack Methodology

The researchers developed a series of proof-of-concept attacks using standard, low-cost NFC tags. Their methodology focused on several key exploitation vectors:

  1. Automatic URI Triggering: Exploiting the Android NFC stack to force the default browser to open a malicious link immediately upon proximity.
  2. Device Fingerprinting: Utilizing the Fingerprintjs2 JavaScript library on a landing page to silently collect unique device identifiers, such as browser version, screen resolution, and installed plugins.
  3. API and Intent Exploitation: Leveraging social media "Web Intents" (Twitter) and the Facebook Graph API to trigger actions like "following" an account or "liking" a page. This takes advantage of the fact that many users remain logged into these services in their mobile browsers.
  4. Location Tracking: Crafting URLs that either include hardcoded location data based on the tag's physical placement or trigger browser-based geolocation requests.
  5. Contact Injection: Using the vCard URI scheme to automatically prompt the device to add a "Malicious Contact" to the address book, facilitating future phishing attempts.

Experimental Setup

The attacks were evaluated across a representative set of hardware and software configurations to ensure broad applicability:

  • Devices: OnePlus 3T, Xiaomi Mi3W, and Samsung C7.
  • Operating Systems: Android versions ranging from 5.1 (Lollipop) to 7.1.1 (Nougat).
  • Browsers: Chrome, Firefox, Pyro, and various native Android browsers.

The Proximity Fallacy

The core security assumption of NFC—that an attacker cannot get within 4cm of a target without being noticed—is fundamentally flawed. Malicious tags do not need to be held by an attacker; they can be hidden under cafe tables, integrated into promotional posters, or placed near legitimate transit readers.

A real-world example of NFC tags used in a retail setting.

Android’s goal of "no-user-intervention" for NFC is the primary driver of this vulnerability. While convenient for tasks like opening a digital menu, it allows a hidden tag to hijack the browser foreground. Furthermore, by placing unique tags at different transit stations, an attacker can track a user’s daily routine more reliably than GPS in indoor or underground environments.

Results and Impact

The study's results demonstrate a universal vulnerability across all tested devices and browsers. Key findings include:

  • Successful Fingerprinting: Researchers successfully generated unique device fingerprints and exfiltrated them to a remote server using simple AJAX calls within the triggered browser window.
  • Social Media Manipulation: Tags successfully triggered "Likes" or "Follows" if the user was logged in, though some modern API versions have since added confirmation prompts.
  • Contact Injection: The vCard attack worked seamlessly, showing how an attacker could inject a "trusted" contact (e.g., "Bank Support") to make future malicious calls appear legitimate.

Conclusion and Mitigation

The primary limitation of this attack is that the Android device screen must be unlocked. While this prevents "pocket-to-pocket" attacks, it offers no protection to users actively using their phones in public spaces.

To mitigate these risks, the authors propose that Android move away from automatic execution. Instead, the OS should either request explicit user permission before opening any NFC-triggered link or place the link in the notification tray (similar to BLE Beacons), allowing the user to choose when—or if—to interact.

Summary updated

BibTeX
@misc{bermejo2017steal,
  author = {Carlos Bermejo and Pan Hui},
  title = {{Steal Your Life Using 5 Cents: Hacking Android Smartphones with NFC Tags}},
  year = {2017},
  eprint = {1705.02081},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/1705.02081},
}
Figure