Similar Posts

Subscribe
Notify of
5 Answers
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
iAmProgrammer
1 month ago

Unfortunately, this is exactly what happens without 2FA, as there is no Chapta or Faceid, without 2FA there is no more security today. In addition passwords always (so I make it at least) 20 characters long (numbers, letters/large+small, underscores, special characters, etc.)

A good PW would be: kyLCg,V(vqb_5g8pVr)uW*u

In addition, use a TOTP (time-based one-time password) as 2FA. It is regenerated every 60 seconds. You can do this, for example, by Google Authenticator. Since in the settings of the respective app and a generated QR code, the Authenticator app creates a code that must then be used for verification.

iAmProgrammer
1 month ago
Reply to  ohneahung91

Basically, the security of 2FA (e.g. via an Authenticator app or via e-mail) is based on the assumption that only you have access to your primary account and the associated communication channels (e-mail, app). Therefore, if the hacker was not logged into your email account and there is no unusual registration, it is unlikely that he could capture the 2FA code directly from the email – provided that all communication paths (e.g. TLS encrypted connections) are correctly secured.

But there are theoretically some attack scenarios that would be possible in other contexts:

  1. Man-in-the-middle attack (MITM):
  2. If the attacker uses an insecure connection (e.g. public WLAN without sufficient encryption) or a compromised network, he could theoretically read the traffic. Modern providers and services usually rely on encryption, so that this would only be possible under special circumstances.
  3. Phishing or Social Engineering:
  4. An attacker could try to “confide” you in the 2FA code by e.g. a fake login page or a message. This is not about the direct interception of the code, but about the user unconsciously releasing his data.
  5. Device compromise:
  6. If your device is already infected or has a vulnerability, an attacker might also access the Authenticator app or the e-mail client and thus get to the code.

Regarding Twitter:

I am currently not aware of known procedures or vulnerabilities that enable Twitter-2FA to be handled in a targeted manner if the entire communication path (including email and authenticator) is properly secured. If Twitter 2FA is correctly implemented, security is based on the ownership of the devices or devices. Accounts – a circumvention is usually not intended and should not be possible without a vulnerability.

In summary:

If the attacker has really not reached your e-mail account and no unusual registration is detectable, it is likely to be another attack vector (such as insecure networks, phishing or a compromised device) that could have captured the 2FA code. In Twitter, unless there are any of these other vulnerabilities, there is no known trick to bypass 2FA.