T01 · Skill Instruction Hijacking
- Location
SKILL.md:29- Finding
Untrusted Remote Instructions Are Retrieved and Followed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its handoff purpose, but it tells agents to follow mutable remote instructions and recommends unpinned external execution, so it should receive human review before installation.
Install only after reviewing the remote-instruction and setup paths. Prefer the web setup flow or a pinned, verified CLI version; do not let an agent blindly follow https://aport.id/skill as executable instructions. Before saving or posting handoffs, redact secrets and sensitive project details, confirm the recipient and channel are approved, and store local copies only where retention is acceptable.
SKILL.md:29Untrusted Remote Instructions Are Retrieved and Followed
SKILL.md:32Unpinned npm Package Is Executed Through npx
The skill tells users to run npx aport-id without pinning a specific package version or integrity source. Because npx fetches the latest published package by default, a compromised maintainer account, malicious update, or dependency hijack could cause arbitrary code execution on the user's machine or agent host.
The skill encourages delivering handoff content through GitHub, Slack, Discord, or messaging tools without any general warning about confidentiality, audience scope, retention, or third-party exposure. Since the handoff can include project status, evidence strings, decision IDs, and contextual notes, posting it externally or broadly could leak sensitive operational or business information.
The skill mandates saving a local copy of the handoff document but does not warn that the document may contain sensitive project details, internal identifiers, recipient information, or decision evidence. This can create unnecessary data at rest on local disks or shared workspaces, increasing the chance of accidental disclosure, persistence beyond need, or pickup by other tools and agents.
This repeats the same unsafe instruction to execute npx aport-id without a pinned version. Unpinned npx execution allows remote code retrieval at runtime, which increases supply-chain risk and could lead to arbitrary code execution if the package or its dependency chain is compromised.