Skill flagged — suspicious patterns detected

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

1688-product-to-ozon

v1.2.1

将1688的商品铺货到俄罗斯电商平台Ozon(上架),通过Ozon官方API实现商品信息的上传和状态查询。适用于需要将单个1688的商品上架到Ozon的场景。

1· 221·0 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name/description (map 1688 products to Ozon and upload them) aligns with the included scripts which call Ozon and AlphaShop APIs. However the registry metadata claims no required environment variables or primary credential while the SKILL.md and scripts clearly require OZON_API_KEY, OZON_CLIENT_ID and ALPHASHOP_ACCESS_KEY/ALPHASHOP_SECRET_KEY. That metadata omission is inconsistent and should be corrected/clarified.
Instruction Scope
SKILL.md and the scripts instruct only to query category mappings, fetch Ozon attributes, translate images via AlphaShop, build Ozon-format JSON and call Ozon APIs. The scripts only read environment variables, make HTTPS requests to api.alphashop.cn and api-seller.ozon.ru, and write local JSON files; they do not attempt to read unrelated system files or network endpoints beyond the documented services.
Install Mechanism
This is an instruction-only skill with bundled Python scripts and a requirements.txt (requests, PyJWT) but no install spec. That is operationally inconsistent: the code will run but dependencies may not be automatically installed by the platform. From a security perspective there is no opaque remote download; code is present and readable, which reduces hidden risk but means the platform will execute provided scripts — review dependencies and runtime environment before running.
!
Credentials
The SKILL.md requires multiple secret environment variables (OZON_API_KEY, OZON_CLIENT_ID, ALPHASHOP_ACCESS_KEY, ALPHASHOP_SECRET_KEY) and an optional OZON_CURRENCY, which are appropriate for the declared integrations. The concern is that the skill registry metadata declared no required envs/primary credential, creating a mismatch that could lead users to install or run the skill without realizing it needs sensitive keys. Ensure you only provide the minimal keys needed and understand where they will be stored (the SKILL.md suggests a path under ~/.openclaw).
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does expect (and document) a local config file path under ~/.openclaw/skillconfig/1688-Product-to-Ozon/ozon_config.json, which is a per-skill config location. It does not modify other skills or system-wide settings in the provided code.
What to consider before installing
This skill appears to implement exactly what it claims (mapping 1688 items and uploading them to Ozon using Ozon + AlphaShop APIs), but pay attention to these points before installing or providing secrets: - Metadata mismatch: The registry metadata states no required env vars, but the SKILL.md and scripts require OZON_API_KEY, OZON_CLIENT_ID and ALPHASHOP_ACCESS_KEY/ALPHASHOP_SECRET_KEY. Do not trust the registry summary alone—use the SKILL.md and code to understand requirements. - Secrets: The skill needs real API keys. Only provide keys you trust and consider using keys with limited scope/permissions. Do not reuse high-privilege/long-lived account credentials if avoidable. - Where credentials are stored: The README/SKILL.md suggests storing Ozon keys in ~/.openclaw/skillconfig/... and AlphaShop keys in the OpenClaw skill env. Confirm how your OpenClaw runtime persists those values and who/what can read them. - Review code before running: The Python scripts are readable and call only the documented endpoints, but you should still review (or run in an isolated environment) to ensure they behave as expected and to install the listed dependencies (requests, PyJWT) from trusted registries. - Operational note: There's no install spec; ensure dependencies are installed and that your runtime environment is isolated (e.g., container or VM) in case you want to limit blast radius. If you need higher assurance, ask the author to update the registry metadata to list required env vars, provide a homepage/source repo, and provide an install spec (or a vetted package) so you can better evaluate provenance. If you cannot verify the author or service (AlphaShop), treat the skill as untrusted and avoid supplying production credentials.

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

latestvk9759rhke6f02dzz0xhdq42z3s83evrw

License

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

Comments