VEO Automation - Auto VEO & Nano Banana on Google Flow 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: hnncdbmjgdcnibomfgiiochojgjfbphg
Permissions (8)
- Browser debugger access
- View open tabs
- Manage downloads
Related extensions
VeoLab - Auto Veo & Nano Banana on Google FlowDeveloper
VEO Automation — Queue, Batch & Auto-Download on Google FlowProductivity
VEO Automation - Auto VEO & FlowProductivity
Batch Generator for Google Flow - Auto Veo 3 Videos & Nano Banana ImagesProductivity
VEO Automation - Auto VEO and Nano Banana on Google FlowProductivity
AutoFlow - Auto Veo & Nano Banana Pro on Google FlowProductivity
Frequently asked questions
Is VEO Automation - Auto VEO & Nano Banana on Google Flow safe to use?
Our latest automated scan rates the Chrome listing of VEO Automation - Auto VEO & Nano Banana on Google Flow at 78/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 VEO Automation - Auto VEO & Nano Banana on Google Flow require?
VEO Automation - Auto VEO & Nano Banana on Google Flow requests 8 permissions. The most significant: Browser debugger access, View open tabs, Manage downloads. See the full breakdown in the security report.
Who develops VEO Automation - Auto VEO & Nano Banana on Google Flow?
VEO Automation - Auto VEO & Nano Banana on Google Flow is published by kylenguyenaws. 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
- 3.6.6
- Current listed version
- 3.6.6
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 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.