📦

審計紀錄

amazon-buy-box-monitor-api-skill - 3 審計

審計版本 3

最新 中風險

Jun 28, 2026, 05:26 PM

Static analysis found network access, environment variable access, shell invocation guidance, and a critical combined-behavior heuristic. Review confirmed these patterns support the documented BrowserAct API workflow, with no prompt injection or confirmed malicious exfiltration found. The remaining risk is medium because the skill handles an API key and sends ASIN and marketplace data to a third-party service.

2
已掃描檔案
200
分析行數
9
發現
codex
審計單位
中風險問題 (3)
Third-Party API Credential Use
The script reads BROWSERACT_API_KEY and sends it as a Bearer token to the BrowserAct API. This is required for the stated function, but it exposes a sensitive credential to a third-party service and needs clear user consent.
External Data Submission to BrowserAct
The script submits the user-provided ASIN and marketplace URL to BrowserAct, then polls for task results. This is expected for the skill, but users should understand that product identifiers and marketplace choices leave the local environment.
API Key Sharing Guidance
The user guidance says to provide the API key to the agent or set it as an environment variable. Asking users to provide secrets in chat increases accidental disclosure risk, even though the script also supports environment variables.
低風險問題 (2)
Documented Script Invocation
The markdown includes a command that runs the bundled Python script with ASIN and marketplace arguments. This is normal for a script-based skill, and the example quotes the arguments.
Static Analyzer False Positives
The weak cryptography and system reconnaissance alerts appear to be caused by product text, ASIN references, status messages, and API response checks. No cryptographic operation or host reconnaissance behavior was found.

偵測到的模式

Bearer Token Sent Over NetworkEnvironment Secret Access

審計版本 2

低風險

May 21, 2026, 08:15 AM

Static analysis flagged 55 potential issues, but all are false positives when evaluated in context. The skill is a legitimate API client for the BrowserAct service. Network requests target only browseract.com, env var access reads only BROWSERACT_API_KEY for authentication, and the shell commands in SKILL.md are markdown documentation examples only. No obfuscation, data exfiltration, or malicious intent was found. Risk factors are documented transparently.

2
已掃描檔案
200
分析行數
6
發現
claude
審計單位
低風險問題 (3)
API key read from environment variable
The script reads BROWSERACT_API_KEY from environment variables using os.getenv(). This is standard practice for API-based skills and the key is only used as a Bearer token for authentication with the BrowserAct service. No credential exfiltration was detected.
Network requests to external API
The script makes HTTP requests to api.browseract.com to start tasks, poll status, and retrieve results. These are legitimate API calls to the documented BrowserAct service. All URLs are hardcoded configuration constants, not user-controlled.
Shell command examples in documentation
SKILL.md contains bash code blocks showing how to invoke the Python script. These are markdown fenced code blocks serving as documentation only. No shell commands are executed from within the markdown file.

審計版本 1

低風險

Apr 28, 2026, 09:14 AM

Security audit completed. All static findings are legitimate API integration patterns. Network access is restricted to the BrowserAct API endpoint only. API key storage uses environment variables (standard secure practice). No command injection vulnerabilities exist. The external_commands detection in SKILL.md are false positives from documentation markdown code blocks.

2
已掃描檔案
200
分析行數
5
發現
claude
審計單位

高風險問題 (1)

API Key Environment Variable Access
Script reads BROWSERACT_API_KEY from environment variables for authentication. This is legitimate credential management pattern.
低風險問題 (2)
Hardcoded API Endpoint URLs
API endpoint URLs are hardcoded in the script. These point to the legitimate BrowserAct API service.
External Commands in Documentation
SKILL.md contains bash command examples for script invocation - these are documentation, not actual command execution