ai-ecommerce-expert-shopee-ecommerce-content

SUSPICIOUS: the business purpose, requested data, and API endpoint are broadly consistent with an ecommerce-content skill, but the execution path depends on a remotely fetched npm CLI at `@latest` and forwards an auth token to that code. This looks more like a supply-chain and credential-forwarding trust issue than confirmed malware; risk would drop if the package were version-pinned and publisher ownership/release history were clearer.

This snippet does not contain overt malware, but it creates a meaningful supply-chain execution risk: it uses npx to run an unpinned '@latest' package (non-deterministic, changeable at runtime) and it passes a sensitive token via environment variables to that external dependency. If the dependency or its supply chain is compromised, the attacker would likely gain the token and the ability to perform arbitrary actions on the host and/or make authenticated API calls. Pin versions, verify integrity, minimize token exposure (scoping/least privilege), and restrict outbound network access for the spawned process.

No direct evidence of malware (no obfuscated payloads, no command execution beyond running a known external package, no direct data theft routines). However, the module dynamically executes an npm dependency via npx using the unpinned '@latest' tag and forwards MCP_TOKEN and API_URL to that dependency. This creates a significant supply-chain and credential-handling risk: if the npm package is compromised or changes behavior, it can access the token and act on the user's behalf.