SMS FRAUD
Jun 27, 2010 at 5:50 pm in GSM by Shri
SMS Fraud is growing rapidly and is becoming a significant issue for all GSM Operators. Nowadays GSM operators are facing numbers of issues related to SMS problem such as Spamming, Spoofing, Fake SMS and illegal use of SMSC Address. Fraud SMS cause :
- Revenue leakage due to faked SMS traffic and SMS spoofing.
- Unpredictable loads on the network due to SMS flooding.
- Increasing Complaint from Mobile subscriber due to SMS Spamming.
Please register to download this file. Its Free
Basics of SMS Fraud (552.4 KiB, 426 hits)
GSM Association official document IR.70 defines each SMS fraud case and their technical aspects. Another GSMA document lists a number of criteria that can identify where an Operator is suspected of fraudulent activity with regards to SMS Fraud Faking & Spoofing.
SMS FRAUD DETECTION AND IDENTIFICATION:
SMS are SS7 signaling messages, which can be monitored with Signaling Surveillance Systems. For SMS Fraud detection two points in the wireless network have to be monitored:
- International SCCP/MAP gateway (IGP).
- The MAP interface to the SMS Center (SMS-C).
So it can be done at the STP (signaling transfer point) by using signaling surveillance system because STP is interfacing SMS-C with external (other than HPLMN) network nodes.
SMS Fraud can be identified primarly by high level survey then low level SS7 message examination which inludes :
Volume Analysis of SMS
- Incoming SMS versus Outgoing
- Frequency Analysis – looking at variations over time
SS7 Message Examination
- Unused MSISDN or IMSI
- Inconsistencies between protocol layers
- Unusual structure or data
- Incomplete transactions
SMS FRAUD CASES:
GSMA document IR.70 defines following 5 cases of SMS fraud :
- Spamming Case
- Flooding case
- Faking Case
- Spoofing Case
- GT Scanning
SMS SPAMMING:
Spamming is an action where the subscriber receives an unsolicited SMS. As an unsolicited SMS, the subscriber did not request to receive this message. The act of spamming does not define the content but only the fact that the SMS was received without solicitation. The content of the spam SMS is incidental to the act. The spam SMS may take on various forms of content to include: commercial information, bogus contest and other message generally intended to invite a response from the receiver. It is important to note that the SMS could be sent from a valid originator and may be correctly billed to the sender.
Technical Aspect : In the Spamming case, there are no specific technical aspects. The spamming Originator could be a single person, a commercial company or a mobile operator.
SMS FLOODING :
When a large number of messages are sent to one or more destinations the act is called SMS flooding. These messages may be either valid or invalid. The value or parameter used to define flooding is the extraordinary number of messages sent. The flooding parameter is compared to the average or normally expected load, and the expected peak value of a selected message flow. When the parameter is unusually high, without other explanation, then this is considered ‘flooding’.
Technical Aspect : The sending of the messages in a case of ‘flooding’ is within the normal methods of sending messages. Consequently, there is no specific technical aspect for this case.
SMS FAKING :
A fake SMS is originated from the international C7 Network and is terminated to a mobile network. This is a specific case when SCCP or MAP addresses are manipulated. The SCCP or MAP originator (for example: SMSC Global Title, or A_MSISDN) is wrong or is taken from a valid originator.
Technical Aspect : The delivery of a Mobile Terminated SM is in two parts –
- The SMS-C uses the destination MSISDN to address a MAP message <Send Routing Information for Short Message>, to the Home Location Register (HLR) for that customer to find out whether the MSISDN is valid, can receive SMS, and if so, to determine the current switch (MSC) that the destination user is registered on. The HLR responds to the SMS-C with the information.
- The SMS-C sends the actual text of the SM to the currently registered MSC and a MAP message <Forward Short Message>. The MSC responds to confirm the message was delivered, and generates a CDR containing all relevant information including the SMS-C address.
In the faking case, the first part is done exactly as described above. However, the second part is changed so that the source address in the MAP message <Forward Short Message> is changed, often to someone else’s SMS-C address. The manipulation of the SMS-C address causes any inter-PLMN SM accounting to be in error, and means that any policing against the apparent Spam generator harms innocent parties and is ineffective against the real Spam generator.
The faking of the source address in the SCCP called party Global Title and the Service Centre Address in the MAP message <Forward Short Message> whilst having the correct equivalent address in the MAP message <Send Routing Information for Short Message> is impossible without considerable efforts by the technical staff running the SMS-C. In other words, it does not happen either by accident, faulty configuration data or as the result of raw text messages received from the Internet. It happens because in most cases it requires a software patch on the SMS-C. Therefore; any instances of this happening are as the result of direct action by SMS-C staff, and probably in conjunction with assistance from the staff of the Associated PLMN.
SMS SPOOFING :
The spoofing case is related to an illegal use of the HPLMN SMS-C by a third party. In this case, a SMS MO with a manipulated A-MSISDN (real or wrong) is coming into the HPLMN network from a foreign VLR (real or wrong SCCP Address).
Technical Aspect :
- To a HPLMN point of view, one subscriber is roaming and sending a SMS. In fact, this is not a real subscriber; the message is not sent by a real mobile but is generated from a specific system with a C7 application.
- The A-MSISDN being used may in fact be real or not depending on the screening in place in the HPLMN SMS-C (Screening on CC+NDC or No A-MSISDN screening in place).
GT SCANNING :
The GT scanning is the fact to send SMS MO to all Global Title address from one mobile operator in order to find unsecured SMS-C (SMS-C that are not controlling the A number).
Technical Aspect :
- Multiple SMS Forward SM Submits are received, generally, from the same mobile MSISDN with the Called SCCP Address and Service Centre Address incremented on each attempt. It would appear that individuals using a mobile with a computer connection are instigating these scans.
- The easiest of these scans to spot are sequential in nature scanning 10,000 GT at a time. It has also been seen randomized scans, though on sorting the data it is clear that blocks are being scanned.
- This type of messaging is picked up in normal statistics in monitoring expected and unexpected combinations of direction, GT and message type.
- There can be no valid reason for such scanning of networks other than locating unsecured SMSC. With simpler computer integration with mobiles and SMS emulation software readily available this type of activity is likely only to increase. It would be desirable for such activities to be reported to the Home PLMN of the originating MSISDN in order to have service removed.


This is not a well-balanced article. It incorrectly classes spoofing as an illegal act, when in fact it’s not. There are both legitimate and illegitimate use cases for SMS spoofing. US legislation is being proposed that prohibits fraudulent use of spoofing, but the non-fraudulent uses are very much legal, and rightly so.
Moreover, it’s a shame SMS spoofing is not easier than it is, because it’s often convenient to send an SMS from a line that the recipient doesn’t necessarily know you by, in which case it would be ideal to spoof the number the other party identifies you by.
Dear Security Expert,
Thanks for your comment. I agree with you on legitimate of SMS Spoofing but the article is about SMS Fraud not SMS Spoofing which includes different types of SMS fraud . If someone change Originating information on a text sent via SMS for legitimate reasons, it might be legal but unauthorized use of HPLMN SMSC by third party is illegal and falls under SMS fraud category as mentioned in article.
Again legality of SMS Spoofing varies worldwide. Some countries completely banned SMS Spoofing e. g. Australia. An official Document AA.50 of GSMA, lists criteria that can identify where an Operator is suspected of fraudulent activity with regards to SMS Spoofing.
Hope this is able to clarify your concern and doubt. We always welcome comments and suggestions on our articles.
Thanks
Shri
hi, Shai,
thank you about this article , please your feedback about this SMS fraud:
oprator A recive TAP files from oprator B about roamer from oprator A within oprator B , But during the TAP analysis oprator A found SMSC adress inside TAP file from operator C ( the adress from their SMS anti spam tool , it is working for the hall country for all the oprator inside the country )
please your support ..
thanks
Dear Ahmed Khallab,
Thanks for your comment.
If I correctly understood, Operator “C” is sending spam to Roamer of Operator “A” who is roaming in to PLMN of Operator “B”. If the message is unsolicited SMS and originator is non valid, Operator “A” can bar SMSC GT of Operator “C” from which these spam SMS is coming. Operator “A” can get SMSC GT of operator “C” in SRI_SM message from Operator “C” to operator “A”. If Operator “C” (SMSC of C) is directly sending spam SMS to Operator “B” through SMPP or any other technique, Operator B can bar SMSC GT of operator “C”.
The better way to resolve these type of issues, Operator “A” can raise concern to Operator “C” with appropriate proof of spamming and request to take action against it.
Thanks
Shri
Hi Shri.
Thanks for the article.
I see the GSMA docs IR.70, IR.71 and AA.50 referenced here and elsewhere on the web, but I haven’t managed to track down the documents themselves. I’ve searched on the GSMA web-site and can’t find them. Do you know where I can find them ?
Thanks.
Hi Bill,
These are the GSMA official documents. You can download these documents from following links:
http://www.gsmworld.com/newsroom/document-library/index.htm
Just select a category, you will get required document.
Thanks
Shri
Dear Shri,
Thank you for this useful article. I have the same problem as Bill had. I can not file those GSMA official documents (IR.70, IR.71 and AA.50) anywhere, including your provided link. Are there any other links where I can find those documents?
Thanks
TC
The documents are not availables in the following link
http://www.gsmworld.com/newsroom/document-library/index.htm
maybe somehwere else but couldn’t find them
Thanks for the articale ,
Suppose that operator A is affected by SMS frude orignated at other operator B :
I know that some vendors provide a solutions to detect and prevent SMS flooding, originated from other operators .
Is there a technical soultions to detect and prevent :
SMS Spamming ,SMS Flooding ,SMS Faking ,SMS Spoofing ,GT Scanning
please tell me about the two scinarios of operatr A is linked to operator A via SS7 or IP based SMS HUB.
Thanks
Khaled
@TC & MO
Hi TC & MO,
To access and download some of the GSMA documents, you should be register member of GSMA.
Thanks
Shri
@Khaled
Hi Khaled,
For IP based SMS HUB, it is responsibility of HUB service provider to monitor SMS fraud and prevent its customer’s network from SMS fraud because in IP, there is no SS7 message used for SMS delivery. In IP connectivity SMS is delivered from SMS HUB to customer’s SMSC or application node through SMPP.
There is no straight forward way of detection of SMS fraud for SS7 connectivity between operator A and operator B without using some technical solution but operator A can take following measure to detect SMS fraud at high level :
- Volume Analysis of SMS : Incoming SMS vs Out going SMS
- Frequency Analysis of SMS : looking at variation over time
For example if Inbound ratio of SRI_SM to FSM from B to A is less, it means some thing is wrong at operator B.
Besides there are several low level message analysis and other criteria on the basis of which an operator can detect SMS fraud. We will cover some criteria in another article soon.
Barring of GT, co-ordination with partners operators and signaling provider (IGP) are the best ways to prevent SMS fraud.
Hello Shri,
I have asked this question in a different topic, but I guess it is more relevant to be asked here, so I am going to repeat the same questions.
I have seen a lot of SMS-MT messages that have different GTs for SCCP Calling and MAP Service Centre Address, but they are all valid. Somehow along the way, some nodes change those GTs so that both are different. In reality, which elements change those GTs, and why?