Security audit

Aport Standup

Security checks for vulnerabilities and agentic risk

Overview

The skill’s main standup purpose is coherent, but it asks agents to follow mutable remote instructions and recommends unpinned local package execution during setup.

Review the setup path before installing. Prefer the web passport flow, avoid running unpinned `npx` commands unless you trust the package source, and do not let the agent follow remote instructions from the APort site as authoritative skill behavior. Treat generated standups as potentially sensitive because they can reveal your work history and policy outcomes.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally

Findings (2)

T01 · Skill Instruction Hijacking

Error

Location: SKILL.md:27
Finding: Unaudited Remote Instructions Can Hijack Agent Behavior
Content: View full analysis
Remediation: View remediation

T08 · Insecure Dependencies

Warning

Location: SKILL.md:30
Finding: Unpinned npm Package Execution Creates a Supply-Chain Risk
Content: View full analysis
Remediation: View remediation
`. 2. Document the expected package registry, publisher identity, package provenance, and release checksum. 3. Prefer installing through a lockfile-controlled project dependency and verify the package integrity recorded in the lockfile. 4. Disable lifecycle scripts during installation where they are not required, and review the package’s executable entry point before use. 5. Avoid silently running the command from the Skill; present it to the user and require explicit confirmation. 6. Prefer a non-executable browser-based onboarding process when practical. 7. Periodically re-audit the pinned version before updating it, rather than automatically resolving the newest available release. ]]>

SkillSpector

Vulnerability Patterns

Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (4)

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The 'When to use this skill' section includes phrases like 'what did I do yesterday?' and 'what have you been doing?', which are common everyday utterances and not narrowly scoped to this specific skill. Because the file does not provide explicit trigger constraints or negative examples, these examples could cause unintended invocation by a generic agent router.
Content: No source excerpt is available for this finding.

Rp1

Medium

Category: MCP Rug Pull
Confidence: 86% confidence
Finding: The skill instructs users to run npx aport-id without pinning a specific package version, which can cause execution of whatever version is currently published. That creates a supply-chain risk: a compromised maintainer account, dependency hijack, or malicious new release could lead to arbitrary code execution on the user's machine.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: The skill directs the agent to fetch decision history associated with APORT_AGENT_ID without discussing consent, minimization, or the sensitivity of audit/history data. If triggered in the wrong context, it could expose behavioral history, timestamps, policy outcomes, and identifiers to a user who did not explicitly request that data or to an unintended audience in a shared/team setting.
Content: No source excerpt is available for this finding.

Rp1

Medium

Category: MCP Rug Pull
Confidence: 86% confidence
Finding: Repeating the unpinned npx aport-id command in the links section reinforces the same unsafe installation pattern and increases the chance users will execute an unreviewed latest version. Because npx fetches and runs code, the exposure is direct code execution rather than a purely informational issue.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.