Google Search Console: Possible Phishing Detected on User Login.
Google Chrome: You just entered your password on a deceptive site.
Sample URLs: N/A.
Other Information
My website is a legitimate private garments management system for H.A Rauf & Co, used exclusively by authorized staff.
I have changed hosting, FTP, database and application passwords, deployed PHP security updates, improved CSRF protection and file upload validation, and updated .htaccess security rules.
Google URL Inspection successfully fetched the original login page. However, the phishing warning remains active, and its exact cause has not been identified.
Please help investigate any malicious content, unauthorized modifications or hosting-related security issues and advise how to resolve this warning.
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
We can’t remove this warning, and we don’t know why Google flagged the site. Only Google can lift a Safe Browsing listing, and only after you request a review in Search Console. Our article on this warning covers the causes, the checks and the review process:
“Possible phishing on user login” with “Sample URLs: N/A” is the situation the article describes for legitimate sites. Google’s scanners judge what a page looks like, not what it’s for, and a bare login form with nothing around it can look like phishing. The article suggests three things for a legitimate site:
Put a public homepage in front of the login that explains what the system is.
Say clearly who runs it. For a private staff system, that means naming H.A Rauf & Co and what the login is for. Contact details help too.
Use only your own branding, with no other company’s names, logos or login-page designs.
Google says that when the report has no example URLs, you should go through those points again and then request a review anyway. In the review request, explain what the site is, who runs it and who the login is for. Request it only once, after the changes are in, because repeated rejected requests can block you from requesting reviews for a while.
Is the login form the first thing anyone sees at your address, or is there already a page explaining what the site is? And have you already submitted a review request in Search Console? That decides whether the next step is changing the page or requesting the review.