Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

4/24/2007
09:35 AM
50%
50%

Dial '72-Duh'

Stupid phishing tricks 101: This new scam is a little too forward

5:35 PM -- There haven't been many creative phishing schemes publicized lately, or maybe it's just that we've become so jaded we hardly notice them anymore. But a new one discovered by SecureWorks is both transparent and tricky at the same time, and apparently effective enough to have several variants still swimming around.

It works like this: The phisher, posing as a bank, emails the victim and asks him to verify his phone number with the bank immediately or risk suspension of his account. (Of course it's perfectly normal for your bank to confirm your phone number and threaten suspension of your account if you don't cooperate. Happens all the time.)

The instructions read very, um, officially:

  • Step 1- Go to your phone and Dial *72
  • Step 2- Dial 7075314910 (XYZ Bank Secure Line)
  • Step 3- Your phone is confirmed
  • You will receive a call from us in 1 h for final verification!
  • If you have confirmed you phone you can continue the update process

    The remainder of the update process is providing their personal information on an official-looking form on the page -- Social Security number, bank account number, credit card number, yada, yada, yada.

    Now, if you have call forwarding on your land line, you may recognize "72" as a common code for that service. So the victim is forwarding his or her calls to the phisher's number (in this case, in Germany). What good does that do the phisher? Well, if the bank gets suspicious about particular transactions, say thousands of dollars wired to an offshore account, and it tries to contact the account-holder, it gets the phisher on the phone instead.

    SecureWorks says this scam was shut down this morning by an ISP, and the phone number killed by the telco, but that it's confident variants of this scam that use call forwarding are still in use out there -- likely with more complex call-forwarding numbers.

    Besides the obvious HELLO, DON'T OPEN SUSPICIOUS EMAILS, ESPECIALLY ONES WITH MISSPELLINGS -- or -- HELLO, DON'T GIVE UP PERSONAL DATA ONLINE advice for avoiding this scam, what's the best clue that you've been hit with it?

    No phone calls.

    — Kelly Jackson Higgins, Senior Editor, Dark Reading

  • SecureWorks Inc.

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    Navigating Security in the Cloud
    Diya Jolly, Chief Product Officer, Okta,  12/4/2019
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Current Issue
    Navigating the Deluge of Security Data
    In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
    Flash Poll
    Rethinking Enterprise Data Defense
    Rethinking Enterprise Data Defense
    Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2019-16772
    PUBLISHED: 2019-12-07
    The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.to...
    CVE-2019-9464
    PUBLISHED: 2019-12-06
    In various functions of RecentLocationApps.java, DevicePolicyManagerService.java, and RecognitionService.java, there is an incorrect warning indicating an app accessed the user's location. This could dissolve the trust in the platform's permission system, with no additional execution privileges need...
    CVE-2019-2220
    PUBLISHED: 2019-12-06
    In checkOperation of AppOpsService.java, there is a possible bypass of user interaction requirements due to mishandling application suspend. This could lead to local information disclosure no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVers...
    CVE-2019-2221
    PUBLISHED: 2019-12-06
    In hasActivityInVisibleTask of WindowProcessController.java there?s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction ...
    CVE-2019-2222
    PUBLISHED: 2019-12-06
    n ihevcd_parse_slice_data of ihevcd_parse_slice.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android...