SafeHop: Scam, Phishing & Fake Shop Blocker extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportEdge listing ID: bgeegkajpphnljofcphlnfnepbmojcgm
Permissions (6)
- Observe web requests
- Execute scripts in pages
- Manage downloads
Related extensions
ScamBlock – Fraudulent Site and Ad BlockerDeveloper Tools
SafeBrowse360 - Scam & Phishing ProtectionMake Chrome Yours
Scam & Phishing Blocker: ScamShieldPrivacy & Security
SafeHop: Scam, Phishing & Fake Shop BlockerTools
Scam Blocker & Ad Blocker with Phishing Protection — AdlessProductivity
Scam Guard - Phishing & Fake Website DetectorProductivity
Frequently asked questions
Is SafeHop: Scam, Phishing & Fake Shop Blocker safe to use?
Our latest automated scan rates the Edge listing of SafeHop: Scam, Phishing & Fake Shop Blocker at 78/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does SafeHop: Scam, Phishing & Fake Shop Blocker require?
SafeHop: Scam, Phishing & Fake Shop Blocker requests 6 permissions. The most significant: Observe web requests, Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops SafeHop: Scam, Phishing & Fake Shop Blocker?
SafeHop: Scam, Phishing & Fake Shop Blocker is published by SafeHop. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Edge
- Checked version
- 1.5.1
- Current listed version
- 1.5.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 2 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.