Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Yunshang Aifei Cli Share
v1.0.0API client for Yunshang Aifei OA system enabling query and write operations on tasks, projects, users, and reports via encrypted REST calls without browser d...
⭐ 0· 47·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The name/description match the implementation: a Python client for the Yunshang Aifei OA API (SM4 encryption, login, query/write endpoints). However the registry metadata lists no required environment variables or credentials while the code and README clearly require AIFEI_USERNAME and AIFEI_PASSWORD in a .env file (and optionally DASHSCOPE_API_KEY). This mismatch between declared requirements and actual code is noteworthy.
Instruction Scope
SKILL.md and the code instruct runtime behavior that goes beyond a simple HTTP client: the login flow uses an automated captcha solver which encodes/POSTs the base64 captcha image to an external /chat/completions endpoint (DashScope). The captcha module will also search local OpenClaw config files for API keys. The skill will read .env, read user config paths (~/.openclaw/openclaw.json and another path), and send image data + a discovered API key to an external model endpoint. These actions access and transmit potentially sensitive data (captcha images and API keys) outside the immediate OA service.
Install Mechanism
There is no install spec; this is an instruction/code-only skill. Dependencies are standard Python packages (gmssl, requests, python-dotenv). Nothing is downloaded from arbitrary URLs or written by an installer beyond normal pip installs mentioned in README.
Credentials
The code requires AIFEI_USERNAME and AIFEI_PASSWORD (read from .env) but the skill metadata declared no required env vars. More importantly, the captcha solver will attempt to auto-locate a DASHSCOPE_API_KEY by reading environment variables or by scanning OpenClaw configuration files for provider apiKey values. That means the skill reads other tools' configuration and may reuse those API keys to call an external service. This is broader credential access than a straightforward OA API client needs and should be considered sensitive.
Persistence & Privilege
The skill is not always:true and is user-invocable. It writes token cache files (.token-prod.json/.token-test.json) into the skill workspace and sets cookies in its requests.Session — normal for a client. It does not modify other skills or system-wide agent settings, but it does read other software's config files (OpenClaw), which is a form of cross-tool credential access worth noting.
What to consider before installing
This skill is a legitimate-looking API client for an internal OA system, but before installing consider the following:
- The code expects AIFEI_USERNAME and AIFEI_PASSWORD in a .env file — the registry metadata did not declare these, so you must provide credentials for it to work. Keep the .env private.
- For captcha solving the module will try to find a DASHSCOPE_API_KEY. If you do not set DASHSCOPE_API_KEY in .env, the module will scan your OpenClaw config (~/.openclaw/openclaw.json and a sibling path) and use any found provider apiKey to call DashScope. If you do not want this skill to access other tool credentials, remove that logic or ensure OpenClaw config does not contain reusable secrets.
- The captcha solver sends base64 image data to an external model endpoint using the discovered API key. That is functional for automation but means an external service will process captcha images; confirm you are comfortable with that data flow and that the API key’s provider is trusted.
- The client caches tokens in files inside the skill workspace. If multiple users share the workspace, tokens could be reused; secure the workspace directory.
If you want to proceed but reduce risk:
- Provide DASHSCOPE_API_KEY explicitly in .env tied to a limited-scope account, or disable/replace the captcha solver with a local/manual step.
- Inspect and, if necessary, remove the code paths that read OpenClaw configuration before running.
- Run the tool only on the intended internal network (the API endpoints are internal IPs) and review the generated .token-*.json files after use.
Given the mismatches and the skill reading other config files for API keys, treat this as suspicious until you confirm or restrict the credential-access behavior.modules/captcha_solver.py:75
Dynamic code execution detected.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97c702gpq4k1srm4c94bqv4m583r3jq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.