Account fraud has been managed historically through the use of keywords. When those became too weak alone to protect account security, multiple-factor-authorization (MFA, or 2FA) was introduced.
At log in, the user gets a SMS asking them to enter the code that they only can hold since it is sent to a device.
However this is now fast becoming obsolete. And a large part of the cybersecurity stakes, and risks, lies in the false sense of security that 2FA or MFA creates.
In simple terms, if you ever click that link in this SMS asking you for an immediate keyword update or the parcel won't be delivered, someone on the other end now has a) your mobile number and b) your login credentials.
No particular 2FA can protect against that kind of attack, or in plainer terms yet, if the cybercriminal directly buys fraudulent tokens on the dark web. Classic MFA is fast becoming obsolete and riskier for users as well as for application security managers relying only on that protocol.
Cyberfraudsters employ several techniques to bypass two-factor authentication (2FA), even when they have already obtained a user's login credentials. Here are some common methods:
Phishing Attacks: Fraudsters often use phishing schemes to trick users into providing their 2FA codes. They might send a fake security alert prompting the user to enter their credentials and the 2FA code on a website that mimics the legitimate one.
Man-in-the-Middle (MitM) Attacks: Here the attacker stays between user and service, intercepting 2-way communications. E.g. when a user logs into a service, the attacker captures both the password and the 2FA token in real-time, allowing them to use these details before the token expires.
SIM Swapping: This involves the attacker convincing the mobile carrier to switch the victim's phone number to a SIM card controlled by the attacker. Once done, any SMS-based 2FA codes are sent to the attacker's device.
Exploitation of Account Recovery Systems: Sometimes, account recovery processes are less secure than the login process and might not require 2FA. Attackers may exploit these weaker paths to gain access without needing to bypass the 2FA.
Malware and Mobile Trojans: Some malware is specifically designed to steal 2FA tokens by infecting the user’s device. Mobile banking trojans, for example, can intercept or forward SMS messages containing 2FA codes to attackers.
Social Engineering: Attackers sometimes use social engineering tactics to persuade users or customer support representatives to disable 2FA on accounts or to provide the necessary information to bypass it.
API Abuse: As SaaS applications frequently rely on APIs for communication between services, attackers exploit insecure APIs to access sensitive data, manipulate services, or cause disruptions. This includes attacks such as unauthorized access, data leakage, and denial of service through API endpoints.
Configuration Errors: Misconfigurations of security settings in the cloud or within the application itself can leave the system vulnerable to attacks. Common issues include improper access controls, unsecured storage buckets, and default credentials.
Insider Threats: These attacks are perpetrated by individuals within the organization who have legitimate access to the system. Malicious insiders can misuse their access to steal data, sabotage systems, or facilitate external breaches.