Skill flagged — suspicious patterns detected

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

Multimodal Extract Attributes

v1.0.0

利用多模态AI分析商品主图,提取视觉特征和提示词。当用户提到分析产品图片、从商品图中提取视觉属性、识别产品Listing中的颜色/形状/材质/风格、反推图片提示词、批量视觉特征提取、将产品图信息转化为结构化数据、视觉属性统计、基于图片的商品分类、main image analysis, image feature...

0· 32·0 current·0 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, SKILL.md, API reference, and included script consistently implement product image attribute extraction via an external LinkFox API — that part is coherent. However, the registry metadata claims "Required env vars: none" while both references/api.md and scripts/multimodal_extract_attributes.py require an API key (LINKFOXAGENT_API_KEY). The undeclared credential is an incoherence that reduces trust.
Instruction Scope
Instructions and the shipped script call an external HTTPS API (https://tool-gateway.linkfox.com/multimodal/extractPromptsFromMainImage) with user-provided product lists and image URLs; this is expected for the stated purpose. The SKILL.md also says the skill should trigger whenever a user mentions extracting structured data from images (including cases where the user doesn't literally say "image analysis"), which broadens activation scope and could lead to unexpected data being sent if triggers are too permissive. The skill does not instruct reading unrelated local files, but it will transmit product metadata and image URLs to the external service.
Install Mechanism
No install spec and only a small helper script are included. There are no downloads from arbitrary URLs or archive extraction. This is low-risk from an install/write-to-disk perspective.
!
Credentials
The only secret required in practice is LINKFOXAGENT_API_KEY (used as the Authorization header). Requesting a single API key is proportionate to calling an external service, but the skill metadata fails to declare this required environment variable. That mismatch (runtime code requiring a key while metadata lists none) is an important coherence issue and a potential deployment surprise for users. No other credentials are requested.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always:false, no config-paths, no modifications to other skills). It can be invoked by the agent per platform default, which is normal; this combined with the external API call is a usage consideration but not a privilege escalation in itself.
What to consider before installing
Key points to check before installing/using this skill: - The skill will send product metadata and image URLs to https://tool-gateway.linkfox.com for analysis. If your images or product data are sensitive or proprietary, verify the service's privacy, retention, and security policies before sending real data. - The code and API docs require an API key (LINKFOXAGENT_API_KEY), but the skill metadata omitted this requirement. Expect to set LINKFOXAGENT_API_KEY in your environment; confirm where to obtain the key and whether the provider is trustworthy. - Confirm the vendor and homepage: the skill metadata lists no homepage and the source is "unknown." Try to verify the publisher (owner ID) and the LinkFox service independently before trusting it with production data. - Limit triggers and test first: because the SKILL.md suggests triggering on broad mentions of image-related tasks, restrict or review automatic activations and test with non-sensitive images to validate behavior. - If you need higher assurance, request disclosure from the publisher about: where images are processed/stored, retention policy, whether images are reused to train models, and whether TLS and authentication are enforced. Also ask them to update the manifest to declare required env vars and provide a homepage or documentation. If you want, I can: (1) point out the exact lines in the files that require the API key, (2) draft a short checklist/email to the publisher requesting the missing information, or (3) suggest safer local or self-hosted alternatives for image attribute extraction.

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

latestvk97dmast92p4a9zkdb6sfcwk118409jb

License

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

Comments