Article

Losing your money: SMS bank phishing attacks in Ireland

SMS phishing, sometimes referred to as ‘smishing’ , is a common tactic used by fraudsters and other criminals in order to trick the recipient into doing something that benefits the fraudsters. It can take many guises, but one of the most impactful, and therefore dangerous, is when bank accounts are phished. In the last few months in Ireland , there have been multiple reports of SMS phishing attacks against account holders of one of the largest banks in Ireland -Bank of Ireland (BOI).

These recent attacks in Ireland share some of the same techniques that Enea has profiled in depth in other countries, but they also have specific ‘spoofing’ twists which may make them far more successful. We will examine them in detail here.

The Steps of the Attack

The attacks that has been occurring in Ireland works in two stages, with two different forms of spoofing. The following is from a real SMS text message that was received by a targeted number, and our analysis at the time:

Part 1: SMS Spoofing

1) First of the all, the target receives a SMS text message purporting to be from BOI (Bank of Ireland). This screenshot contains an SMS text message telling the subscriber they need to log on to a banking website that looks similar to the ‘real’ BOI online banking website www.365online.com. Note the first covid19-related message at the top – this is actually a real communication from the bank, and we will come back to this later.

 

Text SMS message example of Bank of Ireland SMS phishing scam

 

2) If the user goes to the website, they are presented with the following screen. The look and feel are quite similar to Bank of Ireland’s real online banking website, as the front-end code has been copied. Initially what they ask for here is User ID and the last 4 digits of the target’s phone number.

Screenshot of fake Bank of Ireland login page from SMS phishing campaign

 

3) If the target enters in these details, they are asked for further pieces of information – in this case a date of birth and the first 3 numbers from their PIN. This is different from Bank of Ireland’s normal online banking login, which would normally ask for only one of the piece of information.

Screenshot of fake Bank of Ireland login page from SMS phishing campaign

 

4) Regardless of whether the information entered is valid or not, the fraudsters need all 6 digits of the pin, not just the first 3, so in the following screen, they will ask for all of the digits, under the guise of the ‘wrong digits’ being entered the first time.

Screenshot of fake BOI login page from SMS phishing campaign, social engineering tricks user into entering full PIN

 

5) At this point, once all the details are added, the screen goes blank, however a different message could be displayed here if required.

Screenshot of convincing fake Bank of Ireland login page from SMS phishing campaign

Part 2: Voice Spoofing

Now the fraudsters have all the details, and are able to access the target’s account. However, to transfer any money to the fraudsters, they first need to be registered as a payee (a person to whom money can be transferred) on the target’s account. Most banks, including Bank of Ireland, have some level of secondary authentication to confirm the addition of a new payee to their account. In order to get money from the target, the fraudsters need this. While we did not observe these directly, based on media reports of successful attacks, these are the next steps:

6) Using the target’s details (obtained from the malicious website), the attackers log on to the target’s bank account online, and request to add a new payee to the account.

7) A genuine SMS text message is automatically sent by Bank of Ireland to the registered phone number of the account holder, with a Security Code that is required to be inputted online on the account in order to add a payee.

8) The fraudsters then directly ring the target to request the Security Code they received. According to reports, when the fraudsters make this call, they set the originating phone number making the call (the caller) to be the same number as a Bank of Ireland phone number.

 

Analysis of the Attack

As stated earlier, in general, this attack shares many characteristics with bank spam phishing attacks we have seen in other countries:

The phishing SMS was sent in the evening on a public holiday – in this case on Easter Monday (13th of April). Previously, we have shown that bank phishing fraudsters often send their messages during unsocial hours (evenings, weekends and holidays). Also as shown in our previous research fraudsters send more messages after business hours and around weekends. The reason this happens is if the target received a text during unsocial hours there is less chance they can contact security or fraud contacts within a bank. Even though we only have a single example here, it fits into the trend we have seen before – being sent at 8pm, and on a public holiday.

There is wide-scale social engineering involved, the initial message applies a sense of urgency, and typically says the account is disabled or deactivated. It uses a registered URL name: 365online-support[dot]com that resembles the site 365online.com they wish to imitate. The website itself at this address also copied almost verbatim the look and feel of the phished organisation. To further avoid detection, in this case the malicious url was only registered on the day of the attack (April 13th), which is standard for attacks of this type.

Finally, there is no indication that the fraudsters know whether those who receive the phishing SMS have a Bank of Ireland account or not. Here, like in the US, what is probably happening in this case is they simply target particular users (Irish mobile phone users), and with Bank of Ireland being the largest bank in Ireland, a certain percentage of those will have a Bank of Ireland account. This matches reports on twitter of people with no Bank of Ireland account receiving similar messages.

 

Spoofing of the SMS Sender

So, why does the phishing SMS seem to come from Bank of Ireland? What is happening here is the sender address of the SMS – BOI – is being spoofed. ‘BOI’ sender is technically called an alphanumeric short code address, not a typical phone number address. It appears to be in the same thread as other, legitimate BOI communications, because when the handset receives messages from the same sender address, it places them in the same thread. This is why real messages, like the preceding Covid-19 notification, appear to come from the same sender as the phishing SMS (along with any subsequent communications from the bank, using the BOI sender address). In the example below, the message circled in green is legitimate, and the one circled in red is the phishing SMS.

 

 

Clearly, the use of a sender address that seems to come from the bank is a tactic that massively increases the potential ‘believability’ of the phishing SMS. Spoofing of the actual shortcode makes this scam very convincing.

From looking through old twitter reports of this, it seems that this tactic of spoofing the BOI shortcode has been used since at least November 2018, and prior to this it was reported that other shortcodes, and source addresses had been used for spoofing purposes.

Another key point, is what is being ultimately obtained. In this case, the fraudsters don’t just want to get access to the victim’s bank account, they want to transfer money out of it. As a result, they need to do further social engineering to get the Security Code that is sent to the victim. As I mentioned above, to do this they ring the victim and try to convince them to hand it over. Two things help them do this:

The victim is probably feeling uneasy if they receive a security code, as they may suspect something is going wrong from their previous interaction with the spoofing site. A phone call purporting to be from the bank helps them feel that they are being taken care of.

The fraudsters initiate the phone call to the victim, and here they spoof the phone number of the bank. This is the 2nd incident of spoofing in this scam, and helps convince victims to hand over the Security Code details, because it seems legitimate.

 

The Trust Model

Technically speaking, the bank itself has not been hacked, nor its systems compromised. What it is potentially guilty of however, is it’s ‘trust model’. It is probable that the initial trust model of this system would have expected that the bank, and only the bank, could send messages from a BOI SMS address. Even though the bank only uses mobile phone networks for communications to bank account holders, it is reasonable to expect that bank account holders will initially assume that all communications from the same address (BOI) are genuine. Bank of Ireland do provide reminders stating they won’t ask for account details, as well as circulating examples of phishing attacks using the BOI shortcode, but at this stage if they are having to explain why some communications are valid and others not, then there is a lack of security, and a certain percentage of people will be defrauded. As long as BOI do any sort of communication on SMS, and phishing message seem to come from them too, then this confusion will arise. To put it another way, in standard SMS the sender is not authenticated, but the issue is the receiver has formed the impression that it is. There is no way that consumers can tell the difference between a legitimate message and a fake one from their display on a standard handset.

However, a bigger issue is the security of the mobile phone network. Simply put, for SMS, it should not be possible to send messages with an alphanumeric sender from sources that the mobile operator does not permit. Special software is needed to send spoofed SMS like this,  and this software ultimately connects to a messaging centre (SMSC). This means that mobile operators in Ireland, using SMS spam filtering logic, should be able to decide if they wish to block messages from sensitive shortcodes like BOI, if they come from unexpected messaging centres. The same type of logic can also occur with phone calls – incoming calls that come from ‘sensitive’ phone numbers can be blocked, based on their source origin point and other characteristics, although due to the fact that it (the spoofed phone call) is the last stage in that attack, detecting and blocking the spoofed SMS should be the priority.

While this sounds logical to implement, there are often conflicting interests. The Banks’ customers are being defrauded, but the Banks may not have a strong ability to force the mobile operators to put in place systems to make spoofing much harder. Similarly, the mobile operators are the ones who can help reduce the problem, but they often don’t even figure in the conversation as most people assume it is a bank issue only. In addition, it is possible that mobile operators may be reluctant to be seen to try to protect SMS given – in theory at least – it is an unsecured medium, even though in reality it is used to send critical communications.

At the same time, it is often not fair to single out individual banks or mobile phone operators. In this example we talk about Bank of Ireland, but examples of other banks being attacked in a similar way exist (in Ireland and in other places like the UK). Below is a screenshot taken from twitter of a UK bank – HSBC – being targeted in 2018.

 

Text message example of HSBC SMS phishing campaign.

An industry wide effort is needed to tackle these scams – i.e. all banks and mobile operators in a jurisdiction to discuss what is needed to help security of messaging for banks – and other organisations that send sensitive communications, and for the operators to agree and put in place protections for them. These collaborative conversations have already begun in the UK and South Africa, and Enea AdaptiveMobile Securityis happy to be a part of them . The end result is that countries can put in place industry-wide protection, and malicious messages that purport to be from Banks can be detected and blocked. For all enterprises – not just banks – even though SMS has a level of security, enterprises need to be aware that there are potential vulnerabilities to the SMS ecosystem that need to be taken into account when deciding whether to use it as a communication medium. By working with mobile operators, enterprises can determine how they deal with those vulnerabilities, such as by implementing best practices in blocking SMS spoofing and other telecom industry recommended protections. Other specific changes from banks could also be considered, such as multi-factor authentication, in order to raise the security bar higher and make it harder for attackers to use social engineering to steal sensitive information.

It is always upsetting when people are targeted, and far more upsetting and potentially life-changing if they are defrauded successfully. Ultimately the success or failure of these attacks comes down to whether their social engineering is successful or not. Attacks like this will continue, but the fact they are able to successfully spoof source bank SMS addresses gives the fraudsters a massive advantage. While we can, we should warn people to be wary of any text messages, emails or phone calls they receive, unless we want more innocent people in the community to be defrauded. Most importantly, the wider industry within each country should come together and put in place methods and procedures to stop, or at least reduce the effectiveness of, the tactics and techniques these criminals use.

Related insights

Infosecurity Magazine logo

Cyber-criminals Exploit Cloud Storage for SMS Phishing Scams

Read more

Tags: SMS scam

Enea in Mobile Europe

Cyber-criminals using AWS, Google and IBM services to steal data by SMS

Read more

Tags: SMS scam

Exploiting the Cloud: How SMS Scammers are using Amazon, Google and IBM Cloud Services to Steal Customer Data 

Read more

Tags: SMS scam

gsma logo

Establishing MoTIF: The Mobile Threat Intelligence Framework

Read more

Tags: Mobile Security

The fast mode

Enea, Zain KSA to Pilot World’s First Mobile Network Signaling Overlay Technology

Read more

Tags: Mobile Security