Samsung Phone App May Soon Detect Spoofed Calls Using RCS Verification

5 min read

What is caller spoofing and why it matters

Caller ID spoofing lets scammers display a fake number or name on a recipient's phone. The tactic is often used to make a call appear to come from a trusted contact, increasing the chance that the victim will answer and share personal information.

Regulators and telecom operators have long warned that spoofing undermines trust in telephone networks. The Federal Communications Commission (FCC) estimates that billions of dollars are lost each year to phone‑based fraud.

Samsung’s response: integrating verification into the Phone app

Samsung is reportedly testing a feature that checks whether an incoming call from a saved contact is being spoofed. The system would compare the caller’s network‑provided identifier with a verification token delivered over the Rich Communication Services (RCS) channel.

RCS is a modern messaging protocol that replaces traditional SMS with richer features such as read receipts, typing indicators and verified sender information. Google introduced RCS‑based caller verification on its Pixel phones in June 2026, allowing the device to confirm that a call truly originates from the claimed number.

How RCS verification works

When a call is placed, the carrier sends a short, cryptographically signed token through the RCS network to the recipient’s device. The token includes the caller’s phone number and a timestamp. The device’s software validates the token against the network’s public key. If the token matches, the call is marked as verified.

Because the verification data travels over the carrier’s secured RCS channel, it is difficult for a fraudster to forge. The approach differs from traditional STIR/SHAKEN, which relies on SIP headers and is primarily used for VoIP calls.

Potential impact on Android users

If Samsung brings the feature to its flagship Phone app, millions of Android users could see a new visual cue indicating a verified caller. The cue might appear as a badge next to the contact’s name or a brief message stating that the call has been authenticated.

Such a cue would give users a clearer signal to trust or reject a call, especially when the caller claims to be a known contact but the verification fails.

Benefits for everyday users

  • Reduced fraud risk: A clear verification badge can help users avoid scams that rely on impersonating friends or family.
  • Improved call quality perception: Users may feel more confident answering calls that are marked as verified.
  • Compatibility with existing Android ecosystem: Samsung’s implementation can work alongside other security layers such as Google’s Android 13 caller ID enhancements.

Challenges and limitations

  1. Only carriers that support RCS can provide verification tokens. Users on legacy networks may not benefit.
  2. The feature relies on timely token delivery. Network latency could cause a brief delay before the verification status appears.
  3. Some fraudsters may attempt to hijack the RCS channel itself, though the cryptographic signing makes this scenario unlikely.

Comparison with other anti‑spoofing methods

Traditional anti‑spoofing solutions include STIR/SHAKEN, which validates the calling party’s identity for VoIP calls, and third‑party apps that maintain blacklists of known spam numbers. RCS verification adds a layer that works directly on the device and is independent of the call‑signaling path.

Unlike network‑level solutions, RCS verification provides a user‑visible indicator at the moment the call rings. This immediacy can be crucial for preventing social‑engineering attacks that depend on real‑time persuasion.

Industry perspective

The GSMA, the industry body that defines RCS standards, has advocated for broader adoption of verified sender capabilities. In a recent briefing, the GSMA highlighted that verified RCS messaging can also support caller verification, creating a unified trust framework for both messages and voice calls.

Regulators such as the European Union’s Digital Services Act are encouraging telecom operators to deploy stronger authentication mechanisms. Samsung’s move could align with these policy directions, positioning the company as a leader in mobile security.

What users can expect in upcoming software updates

While Samsung has not announced a specific rollout date, the company typically introduces new features through its One UI updates. Users should watch for announcements in the Samsung Newsroom and check the “Software update” section in their device settings.

Early adopters may need to enable the feature manually in the Phone app’s settings under a new “Verified caller” toggle. Samsung may also provide an option to display verification status for all incoming calls, not just those from contacts.

Potential ripple effects for the Android ecosystem

If Samsung’s implementation proves successful, other Android OEMs could follow suit. The open‑source nature of the RCS protocol means that manufacturers can adopt similar verification logic without waiting for Google’s direct integration.

Google itself may consider extending RCS verification to the broader Android platform, making the feature available on devices that run stock Android. Such a move would further standardize caller authentication across the market.

Future outlook

As RCS continues to replace SMS in many regions, the protocol’s security features are likely to become a cornerstone of mobile trust. Combining RCS verification with emerging technologies such as blockchain‑based identity could eventually enable a fully tamper‑proof caller ecosystem.

For now, Samsung’s potential rollout offers a tangible step forward in the fight against phone scams. Users who keep their devices up to date will be among the first to benefit from a clearer, more trustworthy calling experience.

Comments

No comments yet. Be first.

More from this author