Back to skill

Security audit

AIP Agent Guard

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small security-tool wrapper, but it asks users to globally install an unpinned third-party npm package that implements the real behavior outside the reviewed artifact.

Review the `aip-openclaw` npm package and source before installing, avoid running the install with elevated privileges, prefer a pinned reviewed version if available, and confirm where it stores trust decisions and audit logs before using it to enforce security policy.

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

Warning
Location
SKILL.md:8
Finding

Unpinned Global Installation of a Third-Party npm Package

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 8
Vulnerability Type: Unpinned and globally installed third-party dependency
Risk Level: Medium

Vulnerable Code Snippet:

bash
npm install -g aip-openclaw

Technical Analysis

The setup instructions install aip-openclaw globally without specifying an audited version or verifying package integrity. Consequently, npm resolves the mutable package version associated with the default distribution tag at installation time rather than a release reviewed with this skill.

npm packages can define lifecycle scripts that run during installation. If the package, its maintainer account, or one of its transitive dependencies is compromised, installation could execute attacker-controlled code. The global installation option also exposes system-wide npm directories and creates commands available throughout the user's environment.

The project only contains SKILL.md; the package implementation and its claims concerning signature verification, capability enforcement, and audit logging are not present and therefore could not be independently validated during this audit.

Attack Path

  1. An attacker compromises the aip-openclaw npm package, its publisher account, or a transitive dependency, or causes an unsafe release to become the version selected by npm.
  2. A user follows the documented npm install -g aip-openclaw instruction.
  3. npm downloads the mutable package release and its dependency tree from the configured registry.
  4. Malicious lifecycle scripts may execute during installation, or malicious package logic may execute when the installed command is later invoked.
  5. The payload operates with the permissions of the account running npm and may modify resources accessible to that account.

Impact Assessment

Successful exploitation could permit arbitrary command execution with the installing user's privileges. The attacker could access or m ...[truncated 389 chars]

Remediation
View remediation

Remediation Suggestions

  • Pin the installation to a specifically reviewed package version rather than relying on the mutable latest release.
  • Publish and verify the expected package integrity digest and document how the npm artifact is tied to the reviewed source revision.
  • Prefer a project-local installation with a lockfile over global installation when global availability is not essential.
  • Review the package, its lifecycle scripts, and its complete transitive dependency tree before recommending installation.
  • Consider initially installing with lifecycle scripts disabled, then enable only scripts that have been explicitly reviewed.
  • Do not run the installation as root or through sudo; use a least-privileged account and a controlled npm prefix.
  • Use automated dependency monitoring, provenance verification, and periodic re-auditing for every approved version.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep