Back to skill

Security audit

form2api

Security checks for vulnerabilities and agentic risk

Overview

This skill has a coherent form-automation purpose, but it captures and stores authenticated browser traffic and cookies too broadly for users to install without review.

Install only if you understand that it can capture authenticated form traffic, API responses, and live browser cookies. Use it only on systems you own or are authorized to test, avoid sensitive accounts, clear the /tmp outputs afterward, and treat generated docs and cookie values as secrets.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (4)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/extract_cookies.py:121
Finding

Authentication Cookies Are Extracted, Printed, and Cached in Plaintext

Content
View full analysis
str: os.makedirs(CACHE_DIR, exist_ok=True) domain_hash = hashlib.md5(domain.encode()).hexdigest()[:8] safe_domain = domain.replace(".", "_").replace(":", "_") return os.path.join(CACHE_DIR, f"{safe_domain}_{domain_hash}.txt") ``` ```python ws.send(json.dumps({ "id": 1, "method": "Network.getCookies", "params": {"urls": [target_url]} })) result = json.loads(ws.recv()) ws.close() cookies = result.get("result", {}).get("cookies", []) if not cookies: print(f"WARNING: No cookies found for {target_url}", file=sys.stderr) return "" cookie_str = "; ".join([f"{c['name']}={c['value']}" for c in cookies]) return cookie_str ``` ```python if cookie_str: with open(cache_path, "w") as f: f.write(cookie_str) print(f"# Saved to: {cache_path}", file=sys.stderr) print(cookie_str) else: print("ERROR: Failed to extract cookies", file=sys.stderr) sys.exit(1) ``` ### Technical Analysis The script uses Chrome DevTools Protocol `Network.getCookies` to retrieve browser cookies for the target URL. This interface may return sensitive session cookies, including HttpOnly cookies that normal page JavaScript cannot access. The resulting cookie string is: 1. Written unencrypted to a predictable directory under `/tmp`. 2. Created without explicitly enforcing owner-only permissions such as mode `0600`. 3. Retained for up to one hour. 4. Printed directly to standard output, where it may be captured by shell history-adjacent tooling, agent transcripts, CI logs, parent processes, or generated command output. The ...[truncated 1764 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/inject_interceptor.js:32
Finding

Interceptor Indiscriminately Captures Sensitive Request and Response Data

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/analyze_requests.py:279
Finding

Captured Network Data Is Written to Predictable Shared Temporary Files

Content
View full analysis
/scripts/analyze_requests.py /tmp/form_api_raw.json ``` ``` ### Technical Analysis Captured traffic and analyzed request objects are stored under fixed, predictable paths in `/tmp`. The structured candidate objects retain the original captured request data, including request headers, request bodies, and response bodies. The files are opened without explicit owner-only permissions, exclusive creation, symlink protection, per-user isolation, or cleanup. On multi-user or weakly isolated systems, another local actor may be able to read the results if permissions permit. A pre-created symbolic link or manipulated path may also redirect writes where operating-system permissions allow it. Even where the system umask prevents cross-user reads, fixed files permit collisions between concurrent runs and leave sensitive data behind after the Skill finishes. ### Attack Path 1. A local attacker predicts the fixed paths `/tmp/form_api_raw.json` and `/tmp/form_api_analysis.json`. 2. A victim runs the Skill against an authenticated application. 3. Raw or analyzed traffic containing tokens, form values, or protected responses is written to those paths. 4. The attacker reads the files if runtime permissions allow access, or exploits a pre-positioned filesystem object where ...[truncated 750 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
scripts/extract_cookies.py:43
Finding

Unpinned Third-Party Dependency Installation Is Recommended

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (12)

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill describes capturing real API requests from a logged-in session and later extracting cookies, but it does not warn the user that this may expose session cookies, CSRF tokens, authorization headers, and other sensitive authenticated data. In this context, that omission is especially dangerous because the skill's stated purpose is to transform intercepted authenticated traffic into reusable automation artifacts, which can facilitate replay, privilege misuse, or credential leakage if mishandled.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

This script injects a page-level interceptor that hooks both fetch and XMLHttpRequest, then stores full request headers, request bodies, and full response bodies for every captured network call. In skill context, that can expose authentication tokens, session identifiers, PII, CSRF tokens, and sensitive API responses without any user disclosure, minimization, or access control, making the interception capability intrinsically dangerous.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger list is excessively broad and includes generic phrases like automation, scraping, and API discovery, which can cause the skill to activate for benign requests outside its intended scope. In this skill's context, overbroad activation is more dangerous because execution leads directly to interception of authenticated browser traffic and later cookie extraction, increasing the chance of unintended sensitive-data capture.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The invocation instructions do not define sufficient gating conditions before executing sensitive steps, such as confirming authorization, ownership, or awareness that authenticated requests will be captured. Given this skill injects a network interceptor and processes session-bound traffic, ambiguous activation boundaries materially raise the risk of misuse against third-party or internal systems without informed consent.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This markdown file instructs users to extract browser cookies, cache them under /tmp, and send them in curl requests, which affects authentication and sensitive session data. While the examples show how to perform the action, they do not warn users about the privacy/security implications of exposing or reusing cookies.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/output_template.md (reported line 53)May include surrounding context.

调用示例

curl

bash
COOKIE=$(python3 <skill_dir>/scripts/extract_cookies.py {{target_url}})

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The sample code uses subprocess to retrieve cookies and then sends them in a requests call, transmitting session credentials to the target endpoint. The surrounding markdown does not disclose the security impact of sending authenticated requests or caution users to verify the endpoint and authorization context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The script writes filtered request data, including request bodies and response previews, to a fixed world-discoverable path under /tmp without asking the user or minimizing sensitive content. In a multi-user or shared environment, this can expose authentication tokens, personal data, or business payloads to other local processes or users, and the fixed filename also increases the chance of accidental overwrite or unintended reuse.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

This script actively extracts browser cookies via Chrome DevTools Protocol and caches them in /tmp, which can expose live session tokens and enable account or API session hijacking if another local process or user can read the file. The risk is increased because the behavior is automated, the cache location is predictable, and there is no explicit consent flow, warning, permission check, or restrictive file-mode handling for the stored secrets.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The natural-language documentation and status messaging in this file are written in Chinese, but the file does not indicate that the skill is region-specific or offer any language choice. Under the stated policy, forcing a specific language without user opt-in can be a locale-policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
96% confidence
Finding

The module docstring presents the tool description and usage entirely in Chinese, which imposes a specific language choice in the user-facing text. There is no indication that the user can select a different language or that the locale restriction is intentionally limited to a region-specific use case.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The file's docstring and inline user-facing instructions are entirely in Chinese, which imposes a specific language on users without any opt-in or alternative. The policy requires avoiding forced language or locale constraints unless the skill offers a choice or clearly justifies the restriction.

Content

No source excerpt is available for this finding.