TikTok Favourites Remover — Bulk Unfavourite 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: jlfpfaohknfjmbenippjnoilmmbblpjj
Permissions (5)
- Execute scripts in pages
Related extensions
TikTok Favorites, Reposts & Likes RemoverTools
TikTok Remover – Reposts, Favorites & LikesLifestyle
Remove TikTok Likes – Bulk Unlike ToolTools
TikTok Favourites Remover — Clear All FavoritesTools
TikTok Favorites Cleanup - Remove Saved Videos in BulkTools
Favorites Cleaner for TikTok – Unfavorite & Organize Saved VideosMake Chrome Yours
Frequently asked questions
Is TikTok Favourites Remover — Bulk Unfavourite safe to use?
Our latest automated scan rates the Chrome listing of TikTok Favourites Remover — Bulk Unfavourite at 80/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 TikTok Favourites Remover — Bulk Unfavourite require?
TikTok Favourites Remover — Bulk Unfavourite requests 5 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops TikTok Favourites Remover — Bulk Unfavourite?
TikTok Favourites Remover — Bulk Unfavourite is published by AIA. 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.0.4
- Current listed version
- 3.1.1
- Scan date (UTC)
- Assessment status
- Completed
The current store version differs from the checked package. These results describe version 2.0.4; they do not verify version 3.1.1.
Recorded findings: 0 critical and 3 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.