Blur Screen, Blur Text & Redact Screenshots - Blurr.ing 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: idleecfobabckmfpgpmkffebmiiehhid
Permissions (6)
- Execute scripts in pages
- View open tabs
Related extensions
Blur Screen - Sensitive Data ProtectionProductivity
Privacy Blur: Screen Privacy ToolMake Chrome Yours
ScreenBlur: Hide Sensitive Data & Blur Text on PageProductivity
BlurScreen - Blur & Hide Sensitive Info on ScreenProductivity
Blur App - Privacy Blur Tool for Screen Shares & RecordingsProductivity
BlurScreen - Screen Blur Tool for Recording & PrivacyProductivity
Frequently asked questions
Is Blur Screen, Blur Text & Redact Screenshots - Blurr.ing safe to use?
Our latest automated scan rates the Chrome listing of Blur Screen, Blur Text & Redact Screenshots - Blurr.ing at 74/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 Blur Screen, Blur Text & Redact Screenshots - Blurr.ing require?
Blur Screen, Blur Text & Redact Screenshots - Blurr.ing requests 6 permissions. The most significant: Execute scripts in pages, View open tabs. See the full breakdown in the security report.
Who develops Blur Screen, Blur Text & Redact Screenshots - Blurr.ing?
Blur Screen, Blur Text & Redact Screenshots - Blurr.ing is published by Artyom Shimanski. 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.3
- Current listed version
- 1.0.3
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 1 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.