Is Automation 360 safe?
We analyzed Automation 360 version 4.5.0.0's actual code and gave it a 55/100 trust score. Automation 360 is purpose-aligned browser automation, but its…
Bottom line
Automation 360 is purpose-aligned browser automation, but its all-site reach, debugging access, and native-software control create substantial exposure.
What it can access
The extension can operate across all websites and file pages, inspect page data, change fields, and communicate with installed software. [Q1][Q2][Q19] Its debugging features can also request cookies and submitted form data. [Q14]
Security weaknesses
It can execute supplied JavaScript and request cookies or submitted form data through browser debugging. [Q11][Q14] A messaging path also forwards requests without checking the sender, increasing the risk that an unintended caller could trigger privileged actions. [Q19][Q21]
Signs of misuse
Captured automation results are sent to the installed Automation Anywhere software, and configured bots or triggers can act automatically; these behaviors fit the stated purpose. [Q6][Q8] No evidence establishes tracking or referral manipulation. [Q12][Q17]
Code findings
What access does this extension ask for, and does that access make sense for what it claims to do?
It requests all-site page access, tabs, scripting, debugger, and native messaging for enterprise browser automation.
Injects scripts into all HTTP, HTTPS, and file pages and declares tabs, scripting, debugger, nativeMessaging, and all-URL access. — manifest.json:11-112
Which websites can it run on, and can it read or change what appears on those pages?
Automation commands can inspect page structure and text, extract tables and source, click controls, and fill fields.
Routes native-agent requests for navigation, source extraction, JavaScript, triggers, and recording. — ExtensionBackgroundLoader.js:235-290
Implements field changes and page-data extraction. — HTMLExecutor.js:188-224,1370-1443
Can it see sensitive information you type, such as passwords, payment details, messages, or form entries?
It can extract page and form data for a user-configured automation; password values are excluded from normal capture.
Executes element actions and data extraction. — HTMLExecutor.js:1370-1472
Returns an empty value for password inputs. — HTMLCommon.js:526-536
Can it access private browser data such as cookies, signed-in sessions, browsing history, bookmarks, or downloads?
It stores extension options and automation state in Chrome storage; no separate browser-history database access was found.
Stores logging and native-messaging preferences in synchronized extension storage. — options.js:11-40,48-73
Can it access anything else on your device, such as files, location, camera, microphone, clipboard, or installed applications?
No evidence of this behavior was found in the reviewed package.
Declares none of those permissions. — manifest.json:103-112
Does it send information outside your browser? If so, what information is sent, where does it go, and why?
Captured page results and command responses are sent to the installed Automation Anywhere native agent, not directly to an unrelated web server.
Receives requests through a native port and returns automation responses through the same trusted channel. — ExtensionNativeMessaging.js:5-34
Posts serialized action responses back to the native port. — ExtensionContext.js:41-80
Does it download or run code, settings, or instructions supplied by a remote server?
The installed native agent supplies runtime automation instructions, element mappings, and triggers.
Passes native-host messages into the request processor. — ExtensionNativeMessaging.js:28-34
Dispatches supplied navigation, extraction, JavaScript, trigger, and debugger commands. — ExtensionBackgroundLoader.js:235-290
Can it take actions without a clear user request, such as opening pages, redirecting searches, downloading files, or sending requests?
Configured bots and triggers can act automatically, which is expected for an RPA product; no covert autonomous behavior was demonstrated.
Registers triggers and recording operations received from the native agent. — ExtensionBackgroundLoader.js:279-290
Can it change important browser settings, including your proxy, search engine, homepage, privacy settings, or other extensions?
No evidence of this behavior was found in the reviewed package.
Requests no proxy, privacy, or settings permissions. — manifest.json:103-112
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.
Uses descriptive request branches for documented automation operations. — ExtensionBackgroundLoader.js:235-290
Does it use eval(), new Function(), or string-based timers to turn text into executable code?
It executes JavaScript text supplied in an automation request. This is a confirmed RPA feature, not evidence of an active malicious data.
Wraps request-provided javaScriptFunction text and injects it into the selected tab. — ExtensionBrowserAction.js:322-483
Places supplied commandData into a Runtime.evaluate expression when debugger execution is used. — ExtensionDebuggerCommand.js:26-55
Does it track the websites, pages, searches, or links you visit?
No evidence of this behavior was found in the reviewed package.
Handles URL navigation, active-tab lookup, document status, and get-all-URLs requests. — ExtensionBackgroundLoader.js:235-290,364-403
Does it create a persistent ID or browser fingerprint to recognize you?
No evidence of this behavior was found in the reviewed package.
Optional diagnostics write to the browser console and are disabled by default. — AALogger.js:18-97
Does it send cookies, session details, authentication data, or page contents elsewhere?
Debugger-driven automation can request cookies, but normal page capture explicitly withholds password-field values.
Supports Chrome debugger Network.getCookies and request-post-data commands. — ExtensionDebuggerCommand.js:75-99
Does not return password values and labels password elements Protected. — HTMLCommon.js:526-536,648-707
Does it record typing, form entries, clipboard contents, or screenshots?
It can fill forms and record user-selected automation targets, but no general keystroke logger, screenshot capture, camera, or microphone access was found.
Clicks a chosen element and sets its value for an automation step. — HTMLExecutor.js:188-224
Declares no capture, camera, or microphone permission. — manifest.json:103-112
Can a website or remote server send commands that make the extension take actions?
No evidence of this behavior was found in the reviewed package.
Connects to the native agent and dispatches its messages. — ExtensionNativeMessaging.js:5-34
Routes native requests to privileged browser operations. — ExtensionBackgroundLoader.js:235-290
Does it alter links, referral codes, advertisements, shopping carts, or search results?
No evidence of this behavior was found in the reviewed package.
Implements debugger clicks and SetText actions. — HTMLExecutor.js:180-224,1368-1372
Does it redirect or modify web traffic, request headers, downloads, or proxy settings?
It can observe request bodies and cookies through Chrome's debugger for automation recording; it does not install a browser proxy.
Enables Network debugging and reads request post data or cookies on command. — ExtensionDebuggerCommand.js:75-99
Can it communicate with software on the computer or services running on localhost?
It communicates with installed native hosts named automation.bot.browseragent and aa.browser.shim.
Defines both native host identifiers. — Browser.js:1-9
Uses Chrome native messaging to connect and send requests. — BrowserNativeMessaging.js:9-24
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.
Routes native-host messages into command processing. — ExtensionNativeMessaging.js:28-34
Accepts supplied JavaScript and debugger commands. — ExtensionBackgroundLoader.js:271-284
Can ordinary websites access privileged extension features through messaging or exposed files?
No evidence of this behavior was found in the reviewed package.
Allows external connections from every extension ID and two vendor web domains. — manifest.json:94-101
Ignores sender identity and forwards the request unchanged to the native host, returning its response. — ExtensionBrowserShim.js:4-21
Sends the supplied request with chrome.runtime.sendNativeMessage. — BrowserNativeMessaging.js:9-15
Does suspicious behavior activate only for certain users, websites, dates, or remote settings?
No evidence of this behavior was found in the reviewed package.
Lets the user disable native messaging and configure diagnostic logging. — options.js:11-40,48-73
Starts or stops native connections according to that setting. — ExtensionBackgroundLoader.js:58-112
Does it perform hidden resource-intensive work, such as cryptocurrency mining?
No evidence of this behavior was found in the reviewed package.
Observed privileged work is browser automation and recording. — ExtensionBackgroundLoader.js:235-290
Does it change form fields or where a form sends its information?
Configured automations can set input values and submit or click page controls; no covert form-action replacement was demonstrated.
Clicks selected elements and changes their values through the SetText operation. — HTMLExecutor.js:180-224,1368-1372