Needle for YouTube: Channel Search, Watch Later & Block Channels 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: magofcbhfhpfabphcldhodhgehhclokc
Permissions (2)
- Store local data
- Add context menu items
Related extensions
YouTube Channel Blocker & Video FilterLifestyle
YouTube Filters – Hide Channels, Block Keywords, & Filter SearchMake Chrome Yours
YouTube Channel BlockerDeveloper
UTubeFilter: Block Channels, Shorts & WatchedProductivity
YouTube ControlProductivity
Block & Hide Channels for YouTube™ - Channel BlocklistLifestyle
Frequently asked questions
Is Needle for YouTube: Channel Search, Watch Later & Block Channels safe to use?
Our latest automated scan rates the Chrome listing of Needle for YouTube: Channel Search, Watch Later & Block Channels at 86/100 (low 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 Needle for YouTube: Channel Search, Watch Later & Block Channels require?
Needle for YouTube: Channel Search, Watch Later & Block Channels requests 2 permissions. The most significant: Store local data, Add context menu items. See the full breakdown in the security report.
Who develops Needle for YouTube: Channel Search, Watch Later & Block Channels?
Needle for YouTube: Channel Search, Watch Later & Block Channels is published by John Kevin. 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
- 2.4.2
- Current listed version
- 2.4.2
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.