Is Automa safe?
We analyzed Automa version 1.30.02's actual code and gave it a 48/100 trust score. Automa is a powerful browser automation tool with broad access and a…
Bottom line
Automa is a powerful browser automation tool with broad access and a serious remote-control weakness, but no clear evidence of covert abuse.
What it can access
It can access nearly every webpage, sensitive form data, browser tabs, downloads, clipboard contents, and proxy controls for automation.[Q1][Q2][Q3][Q5]
Security weaknesses
Trusted pages and localhost can add workflows without a separate confirmation, and imported workflow code can run in webpages.[Q16][Q21][Q11]
Signs of misuse
No covert collection, deceptive link changes, mining, or secret bundled workflow was demonstrated, though configured workflows can send selected data elsewhere.[Q6][Q17][Q23]
Code findings
What access does this extension ask for, and does that access make sense for what it claims to do?
It has all-site access plus tabs, proxy, alarms, debugger, storage, activeTab, offscreen, webNavigation, scripting, and optional sensitive permissions.
Declares <all_urls>, all-frame content scripts, powerful core permissions, and optional cookies/downloads/clipboard access. — manifest.json:3
Which websites can it run on, and can it read or change what appears on those pages?
Workflows can read, select, extract, click, type, and otherwise modify content in any webpage and frame.
Injects the workflow content script at document_start into all pages and frames. — manifest.json:3
Runs workflow blocks through content scripts, scripting injection, and debugger evaluation. — background.bundle.js:23
Can it see sensitive information you type, such as passwords, payment details, messages, or form entries?
A configured workflow can read forms, messages, page text, credentials entered into workflow storage, and other selected data; no covert collection was demonstrated.
Provides workflow data, variables, and credential storage for use by configured automation. — newtab.bundle.js:85
All-site content access gives workflows access to page data selected by the user. — manifest.json:3
Can it access private browser data such as cookies, signed-in sessions, browsing history, bookmarks, or downloads?
It stores workflows, logs, tables, variables, credentials, account sessions, triggers, and execution state locally, with optional account backup/sync.
Defines local IndexedDB stores and browser storage for workflows, sessions, triggers, and execution state. — background.bundle.js:16,23
Manages remote workflow backup and local workflow/credential storage. — newtab.bundle.js:51,85
Can it access anything else on your device, such as files, location, camera, microphone, clipboard, or installed applications?
Workflows can capture tabs, read the clipboard after permission, download files, and process user-selected CSV, spreadsheet, image, and other workflow files.
Declares screenshot-capable tabs access and optional downloads and clipboardRead permissions. — manifest.json:3
Exposes captureVisibleTab and download operations to workflow execution. — background.bundle.js:23
Does it send information outside your browser? If so, what information is sent, where does it go, and why?
Configured workflows can send extracted data to arbitrary URLs, while signed-in features communicate with Automa and connected Google services. No covert fixed send data out destination was found.
Communicates with https://api.automa.site/v1 for authenticated account features. — background.bundle.js:16
Workflow engine includes HTTP request, Google Sheets, and Google Drive integration blocks. — offscreen.bundle.js:34
Does it download or run code, settings, or instructions supplied by a remote server?
It can import and sync complete workflows, packages, triggers, and team workflows from trusted Automa web services.
Page-event bridge adds workflows, packages, and team workflows into extension storage. — webService.bundle.js:1
Fetches signed-in workflow backups from the Automa API. — newtab.bundle.js:51
Can it take actions without a clear user request, such as opening pages, redirecting searches, downloading files, or sending requests?
Workflows can run automatically on schedules, browser startup, matching page visits, context-menu actions, and other configured triggers.
Registers alarms, startup triggers, visit-web triggers, context-menu triggers, and workflow queues. — background.bundle.js:23
Can it change important browser settings, including your proxy, search engine, homepage, privacy settings, or other extensions?
A workflow can change Chrome's proxy configuration; search engine, homepage, DNS, and privacy-setting changes were not found.
Declares the proxy permission. — manifest.json:3
Exposes proxy.settings.set and proxy.settings.clear to the workflow engine. — background.bundle.js:16
Is any important behavior difficult to inspect because the code is hidden, heavily obfuscated, dynamically generated, or supplied by third parties?
No evidence of this behavior was found in the reviewed package.
Webpack bundle retains module boundaries, product strings, endpoints, and feature names. — background.bundle.js:1-23
Does it use eval(), new Function(), or string-based timers to turn text into executable code?
User-authored or imported workflow JavaScript and preload scripts are deliberately executed in pages, sometimes through debugger Runtime.evaluate. Bundled library new Function uses also exist.
Builds and evaluates workflow callback code through Chrome debugger when CSP blocks injection. — background.bundle.js:23
Creates page scripts from workflow preloadScripts and javascript fields; other new Function sites belong to serialization and i18n libraries. — offscreen.bundle.js:34
Does it track the websites, pages, searches, or links you visit?
It can observe tab URLs, navigation events, frames, matching page visits, and workflow browsing activity.
Declares tabs and webNavigation and injects on all sites. — manifest.json:3
Matches navigation URLs against visit-web triggers and tracks active workflow tabs. — background.bundle.js:23
Does it create a persistent ID or browser fingerprint to recognize you?
Signed-in use stores Automa user/session identifiers, workflow IDs, logs, and trigger identifiers; unrelated advertising fingerprinting was not demonstrated.
Stores user sessions, user IDs, workflow IDs, backup IDs, and execution logs for product features. — background.bundle.js:16,23
Does it send cookies, session details, authentication data, or page contents elsewhere?
It stores Automa and optional Google tokens and can access or modify website cookies after the user grants the optional cookies permission. Custom credentials use a packaged-key encryption scheme.
Lists cookies as an optional permission. — manifest.json:3
Copies the signed-in Automa/Supabase session and Google provider tokens into extension storage. — webService.bundle.js:1
Encrypts credential values using the hardcoded string automa-local-build-pass-key. — newtab.bundle.js:85
Does it record typing, form entries, clipboard contents, or screenshots?
A configured workflow can type into forms and capture visible tabs; no always-on keylogger or silent camera/microphone capture was found.
Exposes screenshot capture and workflow-driven page input operations. — background.bundle.js:23
Requests no camera or microphone permission. — manifest.json:3
Can a website or remote server send commands that make the extension take actions?
Trusted Automa sites and localhost can install workflows through page events, and team workflows can register automatic triggers. Current malicious use was not demonstrated.
Loads webService.bundle.js on Automa domains and any http://localhost page. — manifest.json:3
Accepts page-dispatched add-workflow, add-team-workflow, add-package, and update-package events without a separate extension confirmation. — webService.bundle.js:1
Registers supplied team workflow trigger blocks for later execution. — background.bundle.js:23
Does it alter links, referral codes, advertisements, shopping carts, or search results?
No evidence of this behavior was found in the reviewed package.
Executes content and debugger workflow blocks against target pages. — background.bundle.js:23
Injects workflow preload styles/scripts and main JavaScript into webpages. — offscreen.bundle.js:34
Does it redirect or modify web traffic, request headers, downloads, or proxy settings?
Workflows can issue arbitrary HTTP requests, download files, capture traffic-related page data, and route browsing through a configured proxy.
Declares proxy and all-site access, with optional downloads. — manifest.json:3
Exposes proxy, download, and browser automation operations. — background.bundle.js:16,23
Can it communicate with software on the computer or services running on localhost?
It trusts localhost pages for workflow installation, but no native messaging or shell-command execution was found.
Loads the web-service bridge on http://localhost/* and requests no nativeMessaging permission. — manifest.json:3
Does it decode, decrypt, or unpack hidden data and then execute or inject it?
No evidence of this behavior was found in the reviewed package.
Accepts complete workflow objects from trusted web origins and stores them locally. — webService.bundle.js:1
Registers triggers and executes stored workflows. — background.bundle.js:23
Executes the workflow's javascript and preloadScripts fields in target pages. — offscreen.bundle.js:34
Can ordinary websites access privileged extension features through messaging or exposed files?
A page-event bridge lets scripts on trusted Automa domains and localhost add workflows, packages, and authentication state without sender-level validation or a separate confirmation dialog.
Injects webService.bundle.js into the trusted web origins. — manifest.json:3
Listens for __automa-ext__ custom events and acts on their workflow/package payloads. — webService.bundle.js:1
Does suspicious behavior activate only for certain users, websites, dates, or remote settings?
No evidence of this behavior was found in the reviewed package.
Implements manual execution plus registered automatic trigger types and workflow queues. — background.bundle.js:23
Does it perform hidden resource-intensive work, such as cryptocurrency mining?
No evidence of this behavior was found in the reviewed package.
Execution machinery maps to documented browser-automation, storage, spreadsheet, and integration features. — background.bundle.js:1-23
Does it change form fields or where a form sends its information?
A configured workflow can fill form inputs, click submit controls, or rewrite page behavior. No bundled workflow was found that secretly redirects forms to an unrelated collector.
All-site content and scripting access supports form automation. — manifest.json:3
Executes user-configured page interaction and JavaScript blocks. — background.bundle.js:23