BlurKit - Blur Sensitive Data for Screen Sharing 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: mgkbgadmjmmokapanfiopeaddiebdjmn
Permissions (3)
- Store local data
- Access current tab
- Read clipboard
Related extensions
BlurShield - Hide Sensitive InfoTools
DataBlur: Blur Screen & Hide Sensitive Data for Screen SharingMake Chrome Yours
Blur Screen - Sensitive Data ProtectionProductivity
BlurScreen - Blur & Hide Sensitive Info on ScreenTools
BlurScreen — Screen Blur for Privacy & Screen SharingMake Chrome Yours
BlurSite — hide sensitive info on any pageTools
Frequently asked questions
Is BlurKit - Blur Sensitive Data for Screen Sharing safe to use?
Our latest automated scan rates the Chrome listing of BlurKit - Blur Sensitive Data for Screen Sharing at 79/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 BlurKit - Blur Sensitive Data for Screen Sharing require?
BlurKit - Blur Sensitive Data for Screen Sharing requests 3 permissions. The most significant: Store local data, Access current tab, Read clipboard. See the full breakdown in the security report.
Who develops BlurKit - Blur Sensitive Data for Screen Sharing?
BlurKit - Blur Sensitive Data for Screen Sharing is published by survextanmay@gmail.com. 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.1.0
- Current listed version
- 1.1.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 0 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.