How to fix: URL Flagged as Unwanted Software Distribution
Google Web Risk lists this exact URL as a source of unwanted software: downloads that behave deceptively, are hard to remove, or bundle unrelated software without clear disclosure.
Why it matters
Browsers may block downloads initiated from this page or warn visitors before they proceed, reducing legitimate conversion and signaling a compromised or poorly vetted download pipeline.
This category covers software that does not clearly disclose its behavior, changes browser/system settings without consent, or bundles additional unwanted programs, per Google's Unwanted Software Policy.
How to fix it
- 1Review any downloadable installers or bundled software served from this URL against Google's Unwanted Software Policy.
- 2If this is a false positive, request a review through Google Search Console or https://safebrowsing.google.com/safebrowsing/report_general/.
- 3If a third-party ad network or affiliate script is injecting the flagged download, audit and remove it.
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=UNWANTED_SOFTWARE&uri=https%3A%2F%2Fyourdomain.com%2Fpath" | jq .References
Detected automatically by VulnRadar. The check id is url-flagged-unwanted-software, stable across every scan so you can filter or diff on it.
More reputation checks
Questions
- How severe is URL Flagged as Unwanted Software Distribution?
- VulnRadar rates this high 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-unwanted-software, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does URL Flagged as Unwanted Software Distribution 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.