search-1688-supplier

• Outcome: Pass
• Latest audit: May 28, 2026 · 1:00 PM UTC
• Version: 1.0.4

Overview

This skill appears to do what it says: it searches 1688 suppliers through AlphaShop, using AlphaShop credentials and sending search inputs to that API.

Install only if you trust the publisher and AlphaShop API integration. Configure the AlphaShop keys through the skill environment, avoid pasting secrets into chat, and do not submit private, internal, or signed image URLs unless you are comfortable sending them to AlphaShop.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (6)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 93% confidence
• Finding: The skill requires environment secrets (`ALPHASHOP_ACCESS_KEY` and `ALPHASHOP_SECRET_KEY`) and performs outbound API access, but the manifest does not declare corresponding permissions. Undeclared access to secrets and network creates a transparency and policy-enforcement gap: a host may expose credentials or allow external requests without users/admins being clearly informed at install or review time.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The README instructs users to supply AlphaShop API credentials and submit keywords, product links, or image URLs, but it does not disclose that these inputs are sent to an external third-party service. This creates a privacy and data-handling transparency issue: users may unknowingly transmit proprietary sourcing queries, sensitive product images, or internal URLs to AlphaShop, which could violate organizational policies or user expectations.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

requests>=2.20.0
PyJWT>=2.0.0

• Confidence: 94% confidence
• Finding: The dependency is specified with only a lower bound, so builds may resolve to different versions over time, including versions with newly disclosed vulnerabilities or breaking security behavior. Because this skill appears to make outbound API calls, an unpinned HTTP client dependency increases supply-chain and reproducibility risk.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

requests>=2.20.0
PyJWT>=2.0.0

• Confidence: 94% confidence
• Finding: PyJWT is also left unpinned, which means installations may pull different versions across environments and time, potentially including versions with known JWT validation flaws. For a skill that may authenticate to an external API, unsafe or inconsistent JWT library versions can directly affect token verification or signing security.

Known Vulnerable Dependency: requests — 10 advisory(ies): CVE-2014-1830 (Exposure of Sensitive Information to an Unauthorized Actor in Requests); CVE-2024-47081 (Requests vulnerable to .netrc credentials leak via malicious URLs); CVE-2024-35195 (Requests `Session` object does not verify requests after making first request wi) +7 more

High

• Category: Supply Chain
• Confidence: 97% confidence
• Finding: The requirements include requests without constraining it to a patched release, and the package has multiple published advisories including credential leakage and TLS/session verification issues. In a supplier-search skill that likely performs outbound HTTP requests to external services or user-influenced URLs, these flaws can enable credential exposure, SSRF-adjacent abuse, or weakened transport security.

Known Vulnerable Dependency: PyJWT — 8 advisory(ies): CVE-2026-32597 (PyJWT accepts unknown `crit` header extensions); CVE-2024-53861 (PyJWT Issuer field partial matches allowed); CVE-2022-29217 (Key confusion through non-blocklisted public key formats) +5 more

High

• Category: Supply Chain
• Confidence: 96% confidence
• Finding: PyJWT has several known security advisories affecting token validation behavior, including issuer matching and key confusion classes of issues. If this skill uses JWTs for AlphaShop API authentication or verification, a vulnerable PyJWT version could allow token acceptance under incorrect validation conditions, leading to authentication or authorization bypass.

Static analysis

No suspicious patterns detected.