Back to skill

Security audit

Local Vector Memory

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to be a local memory-search helper, but users should be careful because it installs an unpinned PyPI package and may index private local notes or OpenClaw memory.

Install in an isolated virtual environment, avoid `sudo pip install`, consider pinning or reviewing the `local-vector-memory` package before use, and only reindex directories you are comfortable storing in a local vector database. Treat optional cron or HEARTBEAT.md reindexing as persistent behavior that will keep refreshing indexed local 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

Warning
Location
SKILL.md:16
Finding
Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 16-17 **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium ```bash # Install the package pip install local-vector-memory ``` ### Technical Analysis The skill instructs users to install `local-vector-memory` from PyPI without specifying an exact version or verifying an integrity hash. As a result, the installed code is mutable and may differ from the version that was reviewed when this skill was published. Python package installation can execute package-controlled build or installation logic. This repository contains no vendored implementation, lock file, hash-pinned requirements file, or other mechanism for auditing and reproducing the exact package artifact installed by this command. The documentation also directs the installed package to process potentially sensitive local memory files. Therefore, compromise or unexpected modification of the external package could expose data beyond ordinary vector-search content. ### Attack Path 1. An attacker compromises the package publisher account, package distribution process, or a future package release. 2. The attacker publishes a malicious or backdoored release under the same PyPI package name. 3. A user follows the documented prerequisite and runs `pip install local-vector-memory`. 4. Pip resolves the mutable latest release rather than a previously reviewed version. 5. Malicious package code executes during installation or when the `lvm` command or Python library is invoked. 6. The package accesses files supplied for indexing, stored vector-memory data, environment data available to the process, or other resources permitted by the user's account. ### Impact Assessment Exploitation could permit arbitrary code execution with the privileges of the user running pip or invoking the installed package. The affected scope may include indexed Agent-memory files, the local vector ...[truncated 271 chars]
Remediation
## Remediation Suggestions 1. Pin the package to an exact, reviewed version, for example: ```bash pip install local-vector-memory==<reviewed-version> ``` 2. Distribute a requirements or constraints file containing cryptographic hashes, and install with hash enforcement: ```bash pip install --require-hashes -r requirements.txt ``` 3. Audit and publish the source corresponding to the pinned artifact, including its transitive dependencies. 4. Use a lock file or reproducible build process so users consistently install the reviewed dependency graph. 5. Recommend installation in an isolated virtual environment under a non-privileged account. 6. Avoid running pip with elevated privileges and restrict the package's filesystem access to only the directories needed for indexing. 7. Establish dependency-update review and integrity-monitoring procedures before changing the pinned 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

Static analysis

No suspicious patterns detected.