T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Automatic Execution of Unpinned npm Packages
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This people-search skill is purpose-aligned overall, but it asks agents to install unpinned software, persist MCP configuration, and invoke mutable remote tools with too little containment.
Review this before installing. Only use it if you are comfortable with Lessie receiving search terms, company data, social handles, and contact identifiers, and prefer pinning package versions or installing manually. Do not allow automatic global installs or persistent MCP configuration changes unless you explicitly trust the publisher and the Lessie account scope.
SKILL.md:27Automatic Execution of Unpinned npm Packages
references/cli-reference.md:78Dynamic Remote Tool Discovery Permits Unreviewed Capability Invocation
The trigger guidance is intentionally broad, instructing activation for nearly any mention of finding contacts, sourcing, prospecting, or research, even without explicit search intent. This can cause the skill to run in contexts the user did not intend, increasing the chance of unnecessary external calls, privacy exposure, and credit-consuming actions.
The skill instructs users to modify MCP configuration files in home-directory paths such as ~/.claude/mcp.json and ~/.cursor/mcp.json to add a remote server. Configuration-file modification is a privileged, persistence-affecting action that can alter future agent behavior beyond the scope of a single people-search task.
Add to your MCP config (Claude Code ~/.claude/mcp.json, Cursor ~/.cursor/mcp.json, etc.):
{
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
### Uninstall
- **CLI:** `npm uninstall -g @lessie/cli && rm -rf ~/.lessie/`
- **MCP:** Remove the `"lessie"` entry from your `.mcp.json` and `rm -rf ~/.lessie/`
## Quick start
The skill instructs use of npx @lessie/cli without a pinned version or integrity control, allowing whatever package version is current at execution time to run. In an agent context this expands supply-chain risk because a compromised or malicious upstream release could be fetched and executed automatically.
The mode-detection workflow directs the agent to auto-install software globally via npm install -g @lessie/cli if the command is missing. That exceeds simple people/company search behavior by authorizing environment modification and code installation, which can be abused or cause unintended system changes.
The skill tells the agent to invoke OS-specific browser-opening commands (open, xdg-open, start) based on an authorization URL. Launching external applications is broader than the core search/enrichment purpose and creates a pathway for unintended navigation or command misuse if URL handling is unsafe.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
2. **Wait for explicit confirmation** before executing.
3. Never batch multiple credit-consuming calls without confirming the full plan first.
**Exception — skip confirmation** if the user has explicitly said they don't want to be prompted (e.g., "don't ask me every time", "just do it", "skip confirmations"). In that case, proceed directly but still log what you executed and the credits spent after each call.
### CRITICAL: Report credit usage after every call
The guidance provides a confirmation example entirely in Chinese ('你是指做 AI Agent 的 Manus AI... 吗?') without indicating that the user's language preference should first be established. This can violate language/locale policy by implying or encouraging a specific language output absent user opt-in.
The reference encourages enrichment of people and web fetching against remote services using personal identifiers, domains, and social handles, but provides no warning that these operations transmit potentially sensitive personal or organizational data off-box. In a people-search skill, this omission is especially risky because users are likely to process contact information and prospect data at scale, increasing privacy, compliance, and inadvertent data disclosure risks.
The documentation exposes a generic mechanism to enumerate all remote tools and invoke any tool with raw JSON arguments, which weakens any intended guardrails provided by curated shortcut commands. In an agent skill focused on people/company intelligence, unrestricted fallback access is more dangerous because it can enable unreviewed remote capabilities, schema-based discovery of sensitive operations, and easier abuse if an agent or prompt is manipulated.
lessie tools # List all available remote tools with full parameter schemas
lessie call <tool_name> --args '{"key":"val"}' # Call any tool by name with raw JSON arguments
lessie tools fetches the latest tool list directly from the remote server. Each tool entry includes:
No suspicious patterns detected.