T09 · Insecure Skill Coding Practices
- Location
scripts/daren_search.py:1909- Finding
Spreadsheet Formula Injection in Excel Export
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill can perform the stated creator export task, but it also automates account login, reuses browser sessions, intercepts API traffic, and can save sensitive debug files without enough user control.
Install only if you are comfortable letting this skill automate a logged-in Buyin/Jinritemai business account. Use a dedicated account/profile if possible, review and delete any Desktop debug files, verify the selected account before relying on results, and treat generated Excel files as untrusted because creator-controlled fields are not formula-sanitized.
scripts/daren_search.py:1909Spreadsheet Formula Injection in Excel Export
scripts/daren_search.py:1158Sensitive Login and Account Data Persisted in Desktop Debug Artifacts
requirements.txt:1Unpinned and Unverified Third-Party Dependencies
The documented purpose is simple filtering/export, but the skill also handles credentials, persists sessions via the default Chrome profile, intercepts API/XHR data, manipulates browser storage, and saves debugging artifacts locally. This mismatch is dangerous because users may consent to a narrow data-export task without realizing the skill can access account sessions, collect sensitive tokens or page contents, and leave credential or session material on disk.
The skill performs network access and writes files but does not declare any explicit tool scope or permission boundary. This makes the capability set opaque to reviewers and increases the chance of unintended data access, silent file creation, or privilege creep when the skill is executed in an agent environment.
The skill name includes a CN locale marker and the entire user-facing description is written only in Chinese, with no indication that users may choose another language or that the skill is restricted to a China-specific audience for compliance reasons. This can violate language/locale policy when a skill implicitly forces one language without opt-in.
The script persists a browser profile under the user's home directory and reuses cookies/session state across runs while also automating login. That expands the skill beyond simple filtering/export and creates credential/session exposure risk if the local machine, profile directory, or subsequent runs are compromised.
The browser configuration disables automation indicators and related Selenium flags to evade bot detection. Anti-detection behavior is unnecessary for the stated export task and is a strong signal of attempts to circumvent platform defenses, which can facilitate unauthorized automation at scale.
The code injects JavaScript/CDP hooks to capture full XHR request/response bodies for the internal seekAuthor API, including data not limited to what the visible UI intentionally exposes. Intercepting and retaining raw network responses increases the chance of collecting sensitive fields, bypassing intended access boundaries, and violating user expectations or platform controls.
The script captures and stores full XHR responses without clear user-facing notice, and those responses may contain sensitive account, creator, or internal platform data beyond the final export set. Silent network capture materially increases privacy and compliance risk because users may not realize raw API traffic is being collected in memory and processed.
The script accepts email and password, automates login, and may persist session state, but it provides no strong safeguards for credential handling. In this context, credentials could be exposed through logs, browser profile persistence, screenshots/page dumps during failures, or misuse of the automated session.
After login, the script auto-selects an account and even defaults to the second visible account when multiple accounts are present. This can cause actions and data collection to occur under the wrong identity or tenant, leading to unintended access, privacy issues, and cross-account data exposure.
Saving full page source to local disk for debugging can capture tokens, account identifiers, personal data, or other sensitive HTML/embedded state. Because this happens on error paths and writes to predictable locations like the Desktop, it increases accidental local disclosure risk.
The export function writes structured creator data, including IDs, handles, city, follower counts, and other derived metrics, to a local spreadsheet. The tool announces success after writing, but it does not clearly disclose beforehand that collected third-party data will be stored on disk.
The skill name includes the locale suffix "CN", which indicates a China-specific language or locale constraint. In this file there is no accompanying natural-language justification or indication that the user can opt into that locale, so it may violate the policy against forcing a specific language/locale by default.
The dependency uses a lower-bound version specifier instead of pinning to an exact version, which makes builds non-reproducible and can allow unexpected or vulnerable releases to be installed later. In an automation skill that depends on browser-driving libraries like Selenium, this increases supply-chain and stability risk even if it is not directly exploitable on its own.
selenium>=4.15.0
pandas>=2.0.0
openpyxl>=3.1.0
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Using pandas>=2.0.0 allows any future compatible version to be installed, which weakens build determinism and can introduce vulnerable or behavior-changing releases without review. This is primarily a supply-chain hygiene issue rather than an immediate exploit, but it is still a real security weakness.
selenium>=4.15.0
pandas>=2.0.0
openpyxl>=3.1.0
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
The openpyxl dependency is unpinned, so package resolution may pull different versions over time, including versions with newly disclosed flaws or incompatible behavior. Because this skill writes Excel files, the library is directly in the execution path, making version control important for security and reliability.
selenium>=4.15.0
pandas>=2.0.0
openpyxl>=3.1.0
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Natural-language strings throughout the file assume a Chinese UI and Chinese-language user environment, starting from the module description and continuing through selectors and prompts. The skill does not offer any opt-in or alternative locale handling, which can violate language/locale choice policy when not explicitly justified.
This documentation asserts that the login form is not inside an iframe, yet the calling login flow and input-finding logic include iframe enumeration and interaction paths. That is an active contradiction between the documented page model and actual supported behavior.
The docstring describes a main-page-only structure, but later in the same function the code explicitly iterates over iframes to locate login inputs. This is a direct contradiction, not merely missing detail.