T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s order-processing purpose is coherent, but it directs broad automatic email attachment processing, cloud uploads, Feishu writes, and notifications with too little confirmation and ships without the referenced implementation files.
Review carefully before installing. Only use this with explicit per-run consent for mailbox access and customer document uploads, pin and verify the ADP CLI dependency, and require the publisher to include the referenced scripts/config/demo files before trusting the automation on real orders.
SKILL.md:26Unpinned Global Installation of a Third-Party npm Package
SKILL.md:63Security-Critical Workflow References Missing, Unverifiable Local Components
The skill defines broad natural-language triggers such as '运行一下', '测试订单', and '处理这份订单' to launch a full end-to-end workflow that can read local files, process email attachments, upload source documents, write to Feishu Base, and send notifications. Because these phrases overlap with ordinary conversation and the workflow performs external side effects on potentially sensitive business documents, the skill risks executing high-impact actions without sufficiently explicit, scoped user consent.
The mailbox path is configured to auto-process email attachments whenever the user expresses general intent like '跑邮箱通道' or '给我自动审核', and explicitly instructs the agent not to stop for confirmation unless the user says '只查询不处理'. This is dangerous because mailbox contents are sensitive external data, and automatic downloading, parsing, uploading, and notifying on broad trigger language can cause unintended data access, disclosure, and irreversible workflow actions.
The entire natural-language description and prescribed user-facing phrasing are presented only in Chinese, with no indication that the user may choose another language. This can violate a language/locale policy when a skill implicitly constrains interaction language without opt-in or documented justification.
No suspicious patterns detected.