Google Keep Chrome ExtensionSecurity Analysis

Dynamically creates script elements, potentially loading external malicious code.

Uses eval() to execute dynamic code, a common technique for obfuscation and code injection.

Creates functions from strings, similar to eval(), often used to hide malicious code.

Dynamically sets a script's src attribute to load external code at runtime.

Injects and executes scripts in web pages programmatically.

Uses eval() to execute dynamic code — a common vector for code injection.

JavaScript files are accessible to ALL websites. Any page can load and interact with these scripts, enabling web→extension attacks.

Uses XMLHttpRequest to make network calls.

Modifies window.location to redirect the user, potentially to phishing or malicious pages.

Sends messages via Chrome runtime, could communicate with external services.

Web-accessible resources use <all_urls> or wildcard patterns, exposing resources to every website.

Creates a Web Worker, which runs code in a separate thread — can be used for background computation or crypto mining.

Sets innerHTML directly, which can lead to XSS if used with untrusted data.

Encodes data to base64, may be used for data exfiltration.

String with entropy 5.95 bits — may be encoded/encrypted data

object-src is not set to 'none'. Plugins like Flash can be embedded, which may allow code execution.