T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unverified Global Installation of a Third-Party npm CLI
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This search skill is not malicious, but it asks agents to install a global CLI and may handle cloud credentials in an unsafe, under-scoped way.
Install only if you intentionally want Alibaba Cloud CleverSee handling your searches. Prefer an isolated environment, verify the npm package provenance yourself, avoid entering access-key secrets on the command line, use the narrow EngineSearch permission only, and rotate any credential previously used with the documented command-line secret pattern.
SKILL.md:21Unverified Global Installation of a Third-Party npm CLI
SKILL.md:139Cloud Access-Key Secret Passed Through Command-Line Arguments
The trigger list contains broad phrases such as 'web search', '查资料', and '实时信息', which are likely to match many ordinary user requests and cause the skill to activate in situations beyond its intended scope. Overbroad activation increases the likelihood that users are funneled into this skill's credential and profile-management behaviors unnecessarily, amplifying the risk introduced by the auth-related instructions.
The skill documentation includes credential configuration and profile management flows that go beyond a narrowly scoped web-search capability. Expanding the skill into authentication handling increases the chance an agent will solicit, process, or modify sensitive credentials in contexts where only read-only search behavior was expected, widening the attack surface and enabling unintended account access changes.
Documenting and exemplifying cleversee auth set --mode RamRoleArn --access-key-id <id> --access-key-secret <secret> --arn <arn> introduces a non-search capability that can cause the agent to request or handle long-lived cloud credentials despite the skill's stated purpose being web search. This is dangerous because command-line secret entry can expose credentials through shell history, logs, agent transcripts, or misuse by an over-permissive automation flow.