T09 · Insecure Skill Coding Practices
- Location
scripts/openclaw_login.py:488- Finding
Credentials Can Be Submitted to an Arbitrary HTTP(S) Destination
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be legitimate login automation, but it handles tax-platform credentials with weak destination, browser-session, and persistence controls that users should review carefully.
Install only if you are comfortable with local browser automation handling tax credentials. Use a carefully verified official HTTPS 12366 URL, avoid placing real passwords in shell history, run in an isolated local account or virtual environment, and remove ./chrome_profile after use if you do not want cookies or login state retained.
scripts/openclaw_login.py:488Credentials Can Be Submitted to an Arbitrary HTTP(S) Destination
scripts/openclaw_login.py:627Password Exposed Through Process Arguments
scripts/openclaw_login.py:449Unauthenticated Reuse of an Arbitrary Browser Debugging Endpoint
SKILL.md:33Unpinned Third-Party Dependencies Installed from the Active Package Index
Accepting the username and password as positional command-line arguments exposes credentials through shell history, process listings, audit logs, and task-management tools on many systems. Because this skill handles access to a government tax platform, disclosure of those credentials could enable direct account compromise and access to sensitive taxpayer data.
The skill documentation indicates it uses environment variables and shell-executed commands (pip install, playwright install, and running a Python login script), but it does not declare an explicit tool/permission scope. In an agent ecosystem, missing scope declarations can cause overly broad or opaque execution of sensitive capabilities, especially for a credential-handling login automation skill.
The skill explicitly advertises persistent session storage via ./chrome_profile and login-state reuse, but does not clearly warn users that cookies and authenticated session artifacts will remain on disk. Because this skill automates login to a tax platform using user credentials, retained session data could expose sensitive tax-account access to other local users, malware, or later unintended reuse.
The script stores a persistent Chrome profile in ./chrome_profile, which will retain cookies, session tokens, and potentially autofill or other sensitive browser state after login. In the context of a tax-service login automation skill, that persisted state materially increases the chance of local credential/session theft or unintended account reuse by other local users or later processes.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
creationflags = subprocess.CREATE_NEW_PROCESS_GROUP
else:
creationflags = 0
proc = subprocess.Popen(args, stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL,
creationflags=creationflags if sys.platform == "win32" else 0,
start_new_session=True)
max_wait = 10
Natural-language strings in the docstring and runtime messages are fixed in Chinese, and the script is tailored to a specific Chinese tax platform without any option to select another language. Under the language/locale policy, forcing a language without user opt-in can be a policy violation unless explicitly justified as region-specific.