How to fix: URL Flagged as Phishing / Social Engineering
Google Web Risk lists this exact URL as a known phishing or social-engineering page: one designed to trick visitors into handing over credentials, payment details, or other sensitive information.
Why it matters
Visitors on most major browsers will see a full-page phishing warning before this page loads. If this is your own legitimate site, this listing actively drives away real users and damages trust in the domain.
This listing means Google (or a threat-intel feed it aggregates) has independent evidence this URL impersonates a login, payment, or other trusted flow to collect sensitive input.
How to fix it
- 1If this is a false positive, request a review through Google Search Console (Security Issues report) or https://safebrowsing.google.com/safebrowsing/report_general/.
- 2If the page was compromised or spoofed without your knowledge, take it down or fix it immediately, then request review.
- 3Check whether an old, retired login/checkout page under this exact path is still reachable and was cloned or hijacked.
Code examples
Re-check current status directly against Web Risk
curl -s "https://webrisk.googleapis.com/v1/uris:search?key=$WEB_RISK_API_KEY&threatTypes=SOCIAL_ENGINEERING&uri=https%3A%2F%2Fyourdomain.com%2Fpath" | jq .References
Detected automatically by VulnRadar. The check id is url-flagged-social-engineering, stable across every scan so you can filter or diff on it.
More reputation checks
Questions
- How severe is URL Flagged as Phishing / Social Engineering?
- VulnRadar rates this critical severity in the reputation category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id url-flagged-social-engineering, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does URL Flagged as Phishing / Social Engineering map to?
- It maps to CWE-506. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.