CredSniper - Phishing Framework which supports SSL and capture credentials with 2FA tokens

Easily launch a new phishing site fully presented with SSL and capture credentials along with 2FA tokens using CredSniper. The API provides secure access to the currently captured credentials which can be consumed by other applications using a randomly generated API token. Benefits Fully supporte...

Phishing Framework with 2FA Token Support: CredSniper

Easily launch a new phishing site fully presented with SSL and capture credentials along with 2FA tokens using CredSniper. The API provides secure access to the currently captured credentials which can be consumed by other applications using a randomly generated API token. Benefits Fully supporte...

Deloitte Hacked — Cyber Attack Exposes Clients' Emails

Another day, another data breach. This time one of the world's "big four" accountancy firms has fallen victim to a sophisticated cyber attack. Global tax and auditing firm Deloitte has confirmed the company had suffered a cyber attack that resulted in the theft of confidential information,...

Here’s How Hackers Can Hijack Your Online Bitcoin Wallets

Researchers have been warning for years about critical issues with the Signaling System 7 SS7 that could allow hackers to listen in private phone calls and read text messages on a potentially vast scale, despite the most advanced encryption used by cellular networks. Despite fixes being available...

GSA Bounty: 2FA bypass - confirmation tokens don't expire

Hi there, Because of the limitation of the site, accounts may be locked down for 10 minutes. I found 2 ways to bypass this lock period. First one with the confirmation mail that we get when we sign on. If we get the token this way below, we can change account password and bypass the lock period a...

Hacker Sells 2FA bypass flaw in Poloniex exchange after 2 months wait

By Waqas The sold vulnerability facilitates Bypassing 2FA on Poloniex The This is a post from HackRead.com Read the original post: Hacker Sells 2FA bypass flaw in Poloniex exchange after 2 months wait...

Legal Robot: 2FA manual entry uses wrong encoding

A security researcher discovered that following another change from report 259415, we used the wrong encoding for the manually entered secret. No sensitive data was exposed and there was no security risk, but users were unable to manually register a new TOTP device for about 12 hours...

Legal Robot: 2FA manual entry uses wrong encoding

As in report 260491, a security researcher discovered that following another change from report 259415, we used the wrong encoding for the manually entered secret. No sensitive data was exposed and there was no security risk, but users were unable to manually register a new TOTP device for about ...

Legal Robot: Incorrect email content when disabling 2FA

Hello @team, I found that there is false statement in the 2FA disabled mails sent by the legalrobot. what is the issue? When user is disabling the 2fa authenticator app Registration.He will get a notification regarding the Disabling of the 2FA .the mail structure is like this: 2FA disabled The 2F...

Legal Robot: Lengthy manual entry of 2FA secret

Hello @team, I would like to report on some issue where users are going to face while 2FA authentication.We can see that users need to enter 52 bit code manually for 2FA authentication,which is taking a lot of time and it will be difficult for the user to enter the total 52 bits in the google...

Legal Robot: Missing Issuer parameter on TOTP 2FA

During our 2FA challenge, a security researcher discovered that the Issuer parameter was not set in the TOTP URL that gets turned into a QR Code. While there is no direct security impact, it does make 2FA software tokens more difficult to manage...

Legal Robot: Users with 2FA can have multiple sessions

While going live with additional 2FA options, a security researcher discovered that users that had enabled 2FA no longer executed regular logon hooks. Most of Legal Robot's logon hooks have no security impact, but one action logs out other sessions when a new session begins. While there is no...

Legal Robot: Enhancement: email confirmation for 2FA recovery

While searching for other issues, a security researcher proposed an enhancement to our 2FA account recovery: require email verification for 2FA recovery use. We implemented this change and thank @goodhackonly for an excellent suggestion that makes Legal Robot even more secure...

Legal Robot: 2FA Error Handling on Google Authenticator

While searching for bugs in a recently launched 2FA feature, a security researcher discovered that client-side error handling for 2FA was incomplete and could cause confusing results for users. When 2FA failed, there was no error message returned to the client and the login progress spinner...

Legal Robot: 2FA user enumeration via login

While going live with additional 2FA options, a security researcher discovered that during login, users that had enabled 2FA were prompted for a second factor, even with an incorrect password i.e. LR correctly rejected the login attempt without a second factor, but rejected all attempts for that...

Legal Robot: 2FA user enumeration via password reset

While going live with additional 2FA options, a security researcher discovered that during password reset, users that had enabled 2FA were prompted for a second factor. This made the password reset more difficult, and could have allowed enumeration of users that had enabled 2FA. To some degree, 2...

Legal Robot: Missing link to 2FA recovery code

While going live with additional 2FA options, a security researcher discovered that while we provide a TOTP fallback and Recovery code fallback for users that have enabled U2F, we neglected to do this for TOTP-only users. All users that have enabled TOTP or U2F 2FA should have been able to access...

Legal Robot: Non-functional 2FA recovery codes

While going live with additional 2FA options, a security researcher discovered that users that had enabled 2FA were not able to recover their accounts in case of a missing phone or authentication device. The issue was caused by improper error handling on the client during account recovery...

Nextcloud: bypass of 2FA

Improper protection of the 2FA login made a bypass of the 2FA possible. The bug required to know user credentials but effectively rendered the 2FA ineffective. The issue has been fixed by the Nextcloud team and has been validated by the reporter...

Coinbase: Information disclosure same issue #176002

HI, Reference :- 176002 People use 2fa to protect his / her account from unwanted access and for getting secure from information leak. you were displaying the last 4 digits of a user's phone number after login e.g. "we've send a code to xxx-1234". Industry standard is to show 2 digits instead of ...