What do you think for introducing new feature in BMS to disabling call/sms forwarding.

In countries like India, several scams have been surfaced since last year regarding call forwarding and SMS forwarding, where users are specifically targeted with SMS/Link/WhatsApp messages which have particular number pattern (different for all telecom network provider) like
*401 * <call forwarding number>,
*21*<call forwarding number>#

*67*<call forwarding number>#

*61*<call forwarding number>#

*62*<call forwarding number>#
For different operators, specific numerical USSD code is appended to fraudster number. Dialing such number enables call forwarding and SMS forwarding, intercepting banking OTP leads to financial frauds.
Such numerical pattern is not identified by phishing/scam protection. Need to include pattern detection or provide pattern matching rule in call existing call blocking feature.

Find more posts tagged with

Comments

Flexx

https://community.bitdefender.com/en/discussion/105055/what-do-you-think-for-introducing-new-feature-in-bms-to-disabling-call-sms-forwarding

I am also from India and fully understand the context you’re highlighting. The way these USSD codes function here is quite unique and widely used, which makes addressing this type of scam particularly challenging.

Introducing pattern detection for USSD codes related to call and SMS forwarding in security solutions like Bitdefender Mobile Security for Android would be a highly effective step toward preventing fraud. These codes (*21*, *61*, *62*, *67*, *401*, etc.) are often exploited by fraudsters to intercept banking OTPs by forwarding calls or messages to unauthorized numbers.

At the same time, especially in India, these USSD forwarding codes serve legitimate purposes such as managing missed calls, roaming, and business call management. Therefore, outright blocking these USSD codes could disrupt normal user activity and is not a practical solution.

@Alexandru_BD, @agozob, is there anything you would like to add or correct here?

Regards

Alexandru_BD

Hi,

First, I think telecom providers must implement automated detection systems that identify and block suspicious forwarding codes. If a user suddenly dials a forwarding USSD code after receiving a message, the system should flag it as potentially fraudulent. Secondly, just like cybersecurity experts educate customers about phishing emails, telecom operators should inform subscribers about these scams, there should be more user awareness campaigns on these topics. Conceptually speaking, I think call and sms blocking features could be upgraded to detect suspicious strings that match known forwarding codes, but I'll leave that to @agozob if he wishes to dive into specifics on this one, and tell us if it's something feasible and useful on a larger scale.

I also think that regulators must step in to enforce safeguards. I'm unaware how these concerns are handled in that part of the world, but one thing is certain: the responsibility cannot be left to consumers alone when systemic loopholes are being exploited at scale. I think one of the main challenges here is that telecom operators do not traditionally have the same culture of openness as software or cloud vendors when it comes to vulnerability disclosure, or collaboration with security researchers at large. There are also the telecom protocols which are often tightly controlled and not transparent, and the reality is that operators rarely integrate deeply with antivirus vendors. They may use security vendor technology for network firewalls, DDoS protection, or SMS filtering, etc., but I think collaboration around scam calls is minimal.

Mobile security vendors such as Bitdefender typically protect at the device/app layer, while telecoms focus on the network. The two worlds don’t overlap much..