Browser Lock — Password Protect Chrome & Tabs 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 reportChrome listing ID: agmonmjefejccjgciphlcpndfcppeepd
Permissions (6)
- View open tabs
- Execute scripts in pages
- Delete browsing data
Related extensions
Browser Lock Pro - Browser Password Lock Extension | Chrome Browser LockerMake Chrome Yours
TabLock – Password Protect TabsDeveloper
Tab Locker - Password Protect Browser TabsMake Chrome Yours
Password Lock Tabs & WebpagesProductivity
Chrome Browser LockMake Chrome Yours
LockTab — Password Lock for Your BrowserMake Chrome Yours
Frequently asked questions
Is Browser Lock — Password Protect Chrome & Tabs safe to use?
Our latest automated scan rates the Chrome listing of Browser Lock — Password Protect Chrome & Tabs 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 Browser Lock — Password Protect Chrome & Tabs require?
Browser Lock — Password Protect Chrome & Tabs requests 6 permissions. The most significant: View open tabs, Execute scripts in pages, Delete browsing data. See the full breakdown in the security report.
Who develops Browser Lock — Password Protect Chrome & Tabs?
Browser Lock — Password Protect Chrome & Tabs is published by furia.hub. 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
- Chrome
- Checked version
- 1.0.6
- Current listed version
- 1.0.6
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 5 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.