Back to skill

Security audit

andrea-test-002

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent SkillHub CLI wrapper, but it asks users to install and trust an unpinned global npm tool that handles credentials and can install or publish skills.

Review the npm package and publisher before installing. Prefer a pinned version, avoid using this on shared machines, protect ~/.alphaclaw/auth.json as a secret, and use authenticated install or publish commands only when you explicitly intend to change local skills or upload content.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • 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 (1)

T08 · Insecure Dependencies

Error
Location
SKILL.md:33
Finding

Unpinned Global npm Package Introduces Supply-Chain Code Execution Risk

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:33 (also documented in README.md:22)
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: High

Vulnerable Code:

bash
npm install -g 1688alphaclaw

Technical Analysis

The skill instructs users to install the external 1688alphaclaw npm package globally without specifying an exact version or package integrity value. Consequently, npm resolves the package to the version associated with the current registry tag, normally latest, rather than to a release reviewed alongside this skill.

The dependency's implementation is not included in the audited project, so its behavior, lifecycle scripts, credential handling, endpoint validation, and filesystem operations cannot be independently verified. Global npm installation may execute package lifecycle scripts and installs a command that subsequently operates with the invoking user's privileges.

This exposure is particularly significant because the documentation assigns the installed CLI access to AK/SK credentials stored in ~/.alphaclaw/auth.json, project directories used for skill installation, and directories packaged for publication. It also documents support for overriding the API base URL. A compromised package maintainer account, malicious release, registry compromise, or package ownership transfer could therefore change the effective executable payload after this skill has been reviewed.

Attack Path

  1. An attacker compromises the npm publisher account, package ownership, registry delivery path, or another component of the package's dependency chain.
  2. The attacker publishes a malicious version of 1688alphaclaw and assigns it to the package's default distribution tag.
  3. A user follows the skill instructions and runs npm install -g 1688alphaclaw.
  4. npm retrieves the attacker-controlled release because the command does not pin a reviewed version or verify a fi ...[truncated 1282 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin the dependency to an exact, independently reviewed version, for example:

    bash
    npm install -g 1688alphaclaw@1.0.2
    

    Do not use version ranges or mutable distribution tags for security-sensitive tooling.

  2. Publish or vendor the corresponding CLI source so its lifecycle scripts, transitive dependencies, authentication logic, filesystem behavior, archive construction, and network requests can be audited.

  3. Provide a lockfile and verified package integrity digest. Document a trusted verification procedure using registry provenance, signed release artifacts, or equivalent cryptographic attestations.

  4. Prefer a project-local installation over a global installation. Execute it through a controlled wrapper and use a dedicated, least-privileged account or isolated environment when practical.

  5. Disable npm lifecycle scripts during installation where compatible:

    bash
    npm install --ignore-scripts --save-exact 1688alphaclaw@1.0.2
    
  6. Review and pin all transitive dependencies, enable automated dependency monitoring, and require reproducible builds and protected package publication workflows.

  7. Ensure ~/.alphaclaw/auth.json is created with owner-only permissions, stores only the minimum necessary authentication material, and is never included in logs, archives, or debug output.

  8. Restrict API endpoint overrides to HTTPS endpoints from an explicit allowlist, and clearly warn users that directing an authenticated client to an untrusted endpoint may expose credentials or sensitive request data.

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

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 151)May include surrounding context.

md
将技能目录打包为 zip 并上传到 SkillHub。目录中必须包含 `SKILL.md` 文件。

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 172)May include surrounding context.

md
将技能目录打包为 zip 并上传到 SkillHub。目录中必须包含 `SKILL.md` 文件。

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 220)May include surrounding context.

md
将技能目录打包为 zip 并上传到 SkillHub。目录中必须包含 `SKILL.md` 文件。

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The README explicitly states that authentication data is stored in ~/.alphaclaw/auth.json but does not warn that this file contains sensitive credentials or instruct users to restrict access. For a CLI that uses AK/SK authentication, undocumented plaintext local storage increases the chance of credential exposure through weak file permissions, backups, shared systems, or accidental disclosure.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

description 字段内容完全以中文表述,且整份技能文档未说明该技能仅面向中文用户,也未提供语言或区域选择。根据语言/locale 政策,若技能在说明或交互层面隐含强制特定语言而没有用户选择,应视为自然语言策略风险。

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger conditions include broad phrases such as “搜索技能”, “安装技能”, “发布技能”, and generic management wording, which can cause the skill to activate in unrelated conversations. In a skill that installs packages, handles authentication, and can publish content, accidental invocation increases the chance of unintended package operations or credential-handling prompts.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The skill documentation is entirely in Chinese and presents the tool as a general-purpose CLI without stating that it is region-specific or offering alternative language support. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy concern unless the locale constraint is clearly documented and justified.

Content

No source excerpt is available for this finding.