Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

品氪 OpenApi 开放平台 Skill

v1.0.1

品氪提供的OpenApi开放平台,支持门店、导购、会员、订单、退单、库存、商品、积分、储值、卡券、销售等全链路CRM/SCRM数据同步与管理。通过安全认证的API接口实现第三方系统与品氪平台的数据互通。

0· 75·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name, description, SKILL.md, and the Python code all align: they call Pinkr OpenAPI endpoints for CRM/SCRM operations. Declared API usage (method, appid, data, v) and endpoints in code match the described purpose. However the registry-level metadata (shown earlier) indicates no required env vars/primary credential while SKILL.md and the code require PK_APPKEY (and optionally PK_API_URL) — an inconsistency between manifest and SKILL.md.
Instruction Scope
Runtime instructions and the implemented code focus on making POST requests to the configured PK_API_URL using PK_APPKEY and formatting/saving results. The SKILL.md does not instruct the agent to read unrelated files, system credentials, or exfiltrate data to other endpoints. The code writes results to an 'output' directory under the skill — this is scope-consistent but should be noted.
Install Mechanism
No install spec is provided (instruction-only plus a small Python script). The included requirements.txt only lists 'requests' which is a common dependency. No unusual downloads, URL shorteners, or archive extraction were observed.
!
Credentials
The SKILL.md and script legitimately require a single secret (PK_APPKEY) and an optional PK_API_URL — proportionate to the stated functionality. However the registry metadata at the top of the package incorrectly lists 'Required env vars: none' and 'Primary credential: none', creating an inconsistency about credential needs. This mismatch could confuse users and automated permission checks; confirm that PK_APPKEY is the only credential the skill needs and verify it is sent only to the expected PK_API_URL.
Persistence & Privilege
The skill does not request always:true and is user-invocable. It does not modify other skills or system-wide settings. It does write output files into an 'output' directory under the skill — local persistence limited to that folder.
What to consider before installing
Before installing: (1) Verify the PK_API_URL value points to an official Pinkr endpoint (production vs dev) and that you trust that host. (2) Expect to provide a secret PK_APPKEY — confirm the registry-level metadata omission is just an error and not an attempt to hide credential use. (3) Review the included Python script yourself (it posts form data to the configured URL and writes results to a local 'output' folder); run it in an isolated environment if possible. (4) Avoid supplying unrelated credentials; the skill only needs one app key and an API base URL. (5) If you need higher assurance, ask the publisher for a canonical homepage/source or signed releases, or request the skill be repackaged so registry metadata matches the SKILL.md.

Like a lobster shell, security has layers — review code before you run it.

latestvk973w5wkjp1q3w8hpb6cx329a583tpm0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments