Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk 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: fpclmjagabhijjgopboehemekoalbbfm
Permissions (2)
- Execute scripts in pages
Related extensions
Tweet Bulk Deleter & Unliker Pro : Likes, Comments, Post, RepostProductivity
X / Twitter - Bulk Delete Tweets & LikesProductivity
Tweet Deleter Pro for X (Twitter) - Delete Posts, Likes & RetweetsLifestyle
TweetXDelete — Bulk Delete Posts, Likes & Reposts on XProductivity
Free Tweet DeleterProductivity
Untweet - Bulk delete X and twitter postsLifestyle
Frequently asked questions
Is Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk safe to use?
Our latest automated scan rates the Chrome listing of Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk at 92/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 Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk require?
Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk requests 2 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk?
Unlikely: Unlike All Tweets & Delete X (Twitter) Likes in Bulk is published by Tuğberk Kılıç. 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.0
- Current listed version
- 1.0.0
- 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.