Update: After I requested review using the search console on July 29, 2023, Google sent an email on August 1, 2023 saying that “bell.plus no longer contains links to harmful sites or downloads. The warnings visible to users are being removed from your site.” I am still worried the issue with the NextAuth default sign in page persists. It’s unclear whether this was a manual review or automated scan.
Summary
Google is falsely flagging NextAuth’s default sign in page as phishing. NextAuth is a popular auth library for Next.js. This will get your entire domain, including all subdomains, blocked by Google Chrome for “phishing.” Here is my recommendation:
- If you use NextAuth on your website, immediately stop using the default sign in page.
- Help report an incorrect phishing warning.
- Spread the word! Google needs to patch this before more innocent sites are banned.
- Consider using a browser other than Google Chrome or Firefox (both use the Google block list).
What happened
Today Google Chrome blocked my domain bell.plus
and all of its subdomains for “phishing” due to the NextAuth default sign in page. This is a website I run for free to help students with their schedules. Signing in is optional and only needed if you want to share a schedule.
According to the Google Search console, the “phishing” page is the default NextAuth sign in page:
It is simply a list of buttons to use to sign in with a provider. There is no deception because when a user clicks a provider they are taken to the provider’s website and asked to consent to sharing their identity with this third party. In fact, this sign in page appears on edit.<domain>
, but all subdomains are blocked by Google Chrome.
A quick search shows that this is a recurring pattern with the NextAuth default sign in page:
- Google reports NextAuth api page site as phishing/social engineering
- Site marked as deceptive for Phishing, even when it is not
- My website has been marked as dangerous by Google Chrome
There are likely many more instances of this false-positive that haven’t spoken out publicly. While I hope my own issue is resolved, I write this post to warn others and hopefully spread the word to fix this issue. Falsely flagged websites are bad not only for the website and its users but also because it encourages users to normalize bypassing the security warnings.