Tuesday, March 4, 2025
HomePhishingBeware: Innovative Phishing Threat Targeting Facebook Mobile Users

Beware: Innovative Phishing Threat Targeting Facebook Mobile Users

Published on

SIEM as a Service

Follow Us on Google News

In the past, we came through a number of Phishing campaigns where the attackers using Valid TLD itself for phishing and the Punycode attack demonstrated by Xudong Zheng.

Now hackers find a new way innovative method to create believable URL’s and targeting mobile users, specifically Facebook users.Security experts from Phishlabs came through this new campaign targeting mobile users.

Security expert Crane Hassold says “Instead of attempting to make genuine looking
URLs, threat actors have begun including genuine, legitimate domains within a
longer URL, and padding it with hyphens to hide the real target“.

For Example

hxxp://m.facebook.com-------------validate----step1.rickytaylk[dot]com/sign_in.html

You can see the URL starts with m.facebook.com but the real destination URL here is rickytaylk.com, not  m.facebook.com.

Innovative Phishing Threat Targeting Facebook Mobile Users
Source: PHISHLABS

You can see the screenshot, where you can see only the m.facebook.com and an endless stream which hides the original target address.This smart addition of the Facebook favicon in the address bar looks like the site is exceptionally genuine.

Lack of attention

Inattentive mobile users easily fall into the trap and give away their valuable credentials to the attackers. Generally, these phishing URL’s are transferred through SMS, Chats, and Emails.

Here you can see some more examples.

hxxp://login.Comcast.net-------account-login-confirm-identity.giftcardisrael[dot]com/      
hxxp://accounts.craigslist.org-securelogin--------------viewmessage.model104[dot]tv/craig2/  
hxxp://offerup.com------------------login-confirm-account.aggly[dot]com/Login%20-%20OfferUp.htm  
hxxp://icloud.com--------------------secureaccount-confirm.saldaodovidro[dot]com.br/

Crane Hassold says “it’s highly likely that this tactic is being distributed via SMS phishing or through the social messenger, rather than email”.

One can easily identify the Phishing URL that sent through email by just hovering our the link, but that is not possible if the URL provided through SMS.

Security researchers said they have spotted more than 50 attacks of this type and has a rapid growth from last March.

Hackers not using this method for credential harvesting alone, they use to send more phishing URL’s via status updates or private messages.

Common Defence’s against phishing

  • We know logically the organizations like Facebook will not send the login URL through SMS. You should think that before opening.
  • Always make sure that you entering Login credentials and Card details on a HTTPS page.
  • Don’t open the attachments that you are not expecting.
  • Hover the URL to find the URL’s Integrity.
  • It is always better to type the URL directly in the address bar.
Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Docusnap for Windows Flaw Exposes Sensitive Data to Attackers

A recently disclosed vulnerability in Docusnap's Windows client software (CVE-2025-26849) enables attackers to decrypt...

CISA Warns of Active Exploitation of Microsoft Windows Win32k Vulnerability

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2018-8639, a decade-old Microsoft Windows...

Update Alert: Google Warns of Critical Android Vulnerabilities Under Exploit

Google’s March 2025 Android Security Bulletin has unveiled two critical vulnerabilities—CVE-2024-43093 and CVE-2024-50302—currently under...

BigAnt Server 0-Day Vulnerability Lets Attackers Run Malicious Code Remotely

A critical vulnerability in BigAntSoft's enterprise chat server software has exposed ~50 internet-facing systems...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

JavaGhost: Exploiting Amazon IAM Permissions for Phishing Attacks

Unit 42 researchers have observed a threat actor group known as JavaGhost exploiting misconfigurations...

New Poco RAT Via Weaponized PDF Attacking Users to Capture Sensitive Data

A new variant of malware, dubbed "Poco RAT," has emerged as a potent espionage...

LARVA-208 Hackers Compromise 618 Organizations Stealing Logins and Deploying Ransomware

A newly identified cybercriminal group, LARVA-208, also known as EncryptHub, has successfully infiltrated 618...