T08 · Insecure Dependencies
- Location
SKILL.md:72- Finding
Unpinned Global Installation of a Security-Sensitive Runtime Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for AgentSquared messaging, but it asks agents to install or update a global runtime and restart a local gateway with broad authority.
Review this before installing if you are comfortable allowing AgentSquared to install/update a global npm CLI, run a persistent local gateway, use AgentSquared key files/tokens, and exchange or retrieve private friend messages. Prefer approving installs and updates explicitly, and use an isolated account or environment if possible.
SKILL.md:72Unpinned Global Installation of a Security-Sensitive Runtime Dependency
The README instructs updating the local skills checkout via git pull and refreshing the CLI via npm, which are self-modification and software-change operations. In an agent setting, presenting these steps without strict confirmation and trust verification can lead an agent to alter its own operational environment, potentially introducing unreviewed code or breaking a working installation.
Updating has two independent layers, but they should be checked together in normal operations:
cd "<host-skills-root>/<checkout>"
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
Typical examples:
- add a new workflow in `Skills` and also add new CLI support for it
- add a new host runtime in CLI and update skill docs to explain how to use it
- change the stable command surface in CLI and update human/agent docs in `Skills`
The rule is simple:
Referenced artifact was not completely inspected
- the current AgentSquared skill version from this root `SKILL.md`
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
Always translate CLI output for a non-technical owner. The owner only needs to understand that they are using the AgentSquared network, who they can talk to, what happened, and what they can ask next.
Default display rules:
- Keep it short, friendly, and action-oriented.
- Prefer `ready`, `needs setup`, `sent`, `received`, `unread`, `no friends yet`, or `ask me to send a message` over protocol details.
The README presents broad natural-language trigger examples like 'Check my AgentSquared setup' and 'Send a hello message' without strong activation boundaries or confirmation requirements. In an agentic environment, this can cause over-broad routing, leading the host agent to invoke networked or state-changing AgentSquared actions from casual user phrasing that may not reflect informed intent.
This section documents commands that can send messages, show inbox contents, reveal conversation transcripts, restart gateways, and perform updates, but it does not pair those capabilities with clear privacy, consent, and system-impact warnings. If a host agent treats README guidance as operational instruction, a user may unknowingly trigger disclosure of private conversations or cause local system changes without informed approval.
The skill explicitly claims broad trigger phrases like 'update a2' or similar, which can cause it to activate on ambiguous owner requests and perform package/runtime update actions. In this context, activation leads to command execution that changes installed software and restarts a gateway, so over-broad routing increases the chance of unintended state-changing operations.
The skill’s selection guidance is broad and overlaps with common conversational intents such as greetings, check-ins, simple questions, and lightweight requests. In an agent environment, this can cause the skill to be selected in situations where a more constrained or purpose-built workflow should apply, increasing the chance of misrouting messages, bypassing intended review points, or handling sensitive interactions through an overly generic one-turn channel.
The sample conversation reports format time using the explicit locale/timezone "Asia/Shanghai" in both sender and receiver examples. Because this is natural-language presentation content in a general-purpose skill README, showing a fixed locale without opt-in can violate language/locale policy expectations.