Saturday, January 11, 2025
HomeCVE/vulnerabilityHackers Abused Twilio API To Verify Phone Numbers used For MFA

Hackers Abused Twilio API To Verify Phone Numbers used For MFA

Published on

An unauthenticated endpoint vulnerability allowed threat actors to identify phone numbers associated with Authy accounts, which was identified, and the endpoint has been secured to prevent unauthorized access. 

No evidence suggests the attackers gained access to internal systems or other sensitive data, but as a precaution, it’s crucial to implement additional security measures to mitigate potential phishing attacks that could exploit the leaked phone numbers.

Join our free webinar to learn about combating slow DDoS attacks, a major threat today.

An unauthenticated endpoint in Twilio’s Authy app allowed malicious actors to identify user phone numbers. While no evidence suggests a broader system intrusion or sensitive data exposure, 

They urge all Authy users to update their Android and iOS apps to address the vulnerability, which mitigates the risk of threat actors exploiting the exposed phone numbers for phishing and smishing attacks.  

Authy users should maintain vigilance and carefully examine any text messages that appear to be suspicious. 

A new software update is available for both Android and iOS devices, which addresses various bug fixes, including security vulnerabilities

It is imperative to install this update promptly to preserve the device’s functionality and integrity.  

For Android users, a link has been provided to download the update, while iOS users can acquire the update through the standard software update process on their devices. 

Twilio recognizes a security incident and apologizes for the disruption, as their Security Incident Response Team (T-SIRT) is currently investigating the issue and will provide updates as the situation evolves. 

This incident underscores the critical role of T-SIRT in proactively identifying security vulnerabilities, implementing preventative measures to mitigate risks, and taking corrective actions in the event of a breach. 

T-SIRT’s swift response and ongoing communication are essential to minimizing the impact of security incidents and maintaining customer trust.

If users are unable to access the Authy account due to login issues or lost access to the registered phone number, contacting Authy support is the recommended course of action. 

Their specialists will address the request and collaborate to restore functionality to the Authy account, which may involve troubleshooting login problems or initiating a phone number change procedure.

"Is Your System Under Attack? Try Cynet XDR: Automated Detection & Response for Endpoints, Networks, & Users!"- Free Demo

Raga Varshini
Raga Varshini
Varshini is a Cyber Security expert in Threat Analysis, Vulnerability Assessment, and Research. Passionate about staying ahead of emerging Threats and Technologies.

Latest articles

QSC: Multi-Plugin Malware Framework Installs Backdoor on Windows

The QSC Loader service DLL named "loader.dll" leverages two distinct methods to obtain the...

Weaponized LDAP Exploit Deploys Information-Stealing Malware

Cybercriminals are exploiting the recent critical LDAP vulnerabilities (CVE-2024-49112 and CVE-2024-49113) by distributing fake...

New NonEuclid RAT Evades Antivirus and Encrypts Critical Files

A NonEuclid sophisticated C# Remote Access Trojan (RAT) designed for the.NET Framework 4.8 has...

Hackers Targeting Users Who Lodged Complaints On Government portal To Steal Credit Card Data

Fraudsters in the Middle East are exploiting a vulnerability in the government services portal....

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

QSC: Multi-Plugin Malware Framework Installs Backdoor on Windows

The QSC Loader service DLL named "loader.dll" leverages two distinct methods to obtain the...

Weaponized LDAP Exploit Deploys Information-Stealing Malware

Cybercriminals are exploiting the recent critical LDAP vulnerabilities (CVE-2024-49112 and CVE-2024-49113) by distributing fake...

Juniper Networks Vulnerability Let Remote Attacker Execute Network Attacks

Juniper Networks has disclosed a significant vulnerability affecting its Junos OS and Junos OS...