Back to skill

Security audit

Wip Universal Installer

Security checks for vulnerabilities and agentic risk

Overview

This installer has a coherent broad installation purpose, but it can make persistent agent and global system changes from repository contents with unsafe command and path handling.

Install only after reviewing the target repository and this installer’s actions. Avoid running it automatically from an agent on your main machine; prefer an isolated environment. Be especially careful with --dry-run, remote repo targets, Claude Code hooks, MCP registrations, and any repo whose package name, scripts, or claudeCode.hook metadata you have not inspected.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (4)

T09 · Insecure Skill Coding Practices

Error
Location
install.js:758
Finding

Shell Command Injection Through Unescaped CLI Arguments and Repository URLs

Content
View full analysis
a.startsWith('--')); const rawTarget = process.argv[2]; execSync(`ldm install ${rawTarget} ${flags.join(' ')}`, { stdio: 'inherit' }); ``` The same unsafe delegation is repeated after bootstrapping LDM OS: ```javascript const flags = args.filter(a => a.startsWith('--')); const rawTarget = process.argv[2]; try { execSync(`ldm install ${rawTarget} ${flags.join(' ')}`, { stdio: 'inherit' }); process.exit(0); } catch (delegateErr) { if (!JSON_OUTPUT) console.error(' ldm install failed. Falling back to standalone installer.'); } ``` The standalone clone fallback also interpolates an untrusted URL into shell commands: ```javascript if (target.startsWith('http') || target.startsWith('git@') || target.match(/^[\w-]+\/[\w.-]+$/)) { const isShorthand = target.match(/^[\w-]+\/[\w.-]+$/); const httpsUrl = isShorthand ? `https://github.com/${target}.git` : target; const sshUrl = isShorthand ? `git@github.com:${target}.git` : target.replace(/^https:\/\/github\.com\//, 'git@github.com:'); const repoName = basename(httpsUrl).replace('.git', ''); repoPath = join('/tmp', `wip-install-${repoName}`); try { if (existsSync(repoPath)) { execSync(`rm -rf "${repoPath}"`); } try { execSync(`git clone "${httpsUrl}" "${repoPath}"`, { stdio: 'pipe' }); } catch { if (existsSync(repoPath)) execSync(`rm -rf "${repoPath}"`); execSync(`git clone "${sshUrl}" "${repoPath}"`, { stdio: 'pipe' }); } } } ``` ### Technical Analysis `execSync()` executes string commands through a shell. `rawTarget`, arbitrary arguments beginning with `--`, `httpsUrl`, and `sshUrl` are incorporated without shell escaping or strict validation. Quotation marks around the clone UR ...[truncated 1298 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
install.js:596
Finding

Package-Name Path Traversal Enables Arbitrary Deletion and Writes Under the User Home Directory

Content
View full analysis
!src.includes('.git') && !src.includes('node_modules') && !src.includes('ai/') }); if (existsSync(join(ldmDest, 'package.json'))) { try { execSync('npm install --omit=dev', { cwd: ldmDest, stdio: 'pipe' }); ok(`LDM: dependencies installed`); } catch { skip(`LDM: no deps needed`); } } ``` The same untrusted name controls Skill deployment: ```javascript function installSkill(repoPath, toolName) { const skillSrc = join(repoPath, 'SKILL.md'); const ocSkillDir = join(OC_ROOT, 'skills', toolName); const ocSkillDest = join(ocSkillDir, 'SKILL.md'); ``` ### Technical Analysis `path.join()` normalizes `..` components. It does not guarantee that the resulting path remains beneath the intended parent directory. A local or cloned repository can provide a malformed `package.json` name such as `../../.ssh`. The code does not enforce npm package- ...[truncated 1483 chars]
Remediation
View remediation

T03 · Remote Payload Retrieval and Execution

Error
Location
install.js:741
Finding

Unrequested, Unpinned Global LDM OS Installation Occurs Before Dry-Run Enforcement

Content
View full analysis
a.startsWith('--')); const rawTarget = process.argv[2]; try { execSync(`ldm install ${rawTarget} ${flags.join(' ')}`, { stdio: 'inherit' }); process.exit(0); } catch (delegateErr) { if (!JSON_OUTPUT) console.error(' ldm install failed. Falling back to standalone installer.'); } } } ``` ### Technical Analysis The bootstrap retrieves the current registry-selected version of `@wipcomputer/wip-ldm-os` and installs it globally without an explicit confirmation step or an exact version. npm installation can execute package lifecycle scripts, and the newly installed `ldm` executable is immediately invoked. This happens before the standalone installer applies its `DRY_RUN` behavior. Therefore, a command presented as detection-only can still modify global npm state, download code, execute package installation scripts, and introduce a global executable. The behavior exceeds the minimum privileges necessary for interface detection. It also expands th ...[truncated 1050 chars]
Remediation
View remediation

T06 · System Persistence

Error
Location
install.js:234
Finding

Untrusted Repositories Can Execute npm Lifecycle Scripts and Install Persistent Agent Hooks

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Findings (18)

Agent Config Directory Access

High
Category
Agent Snooping
Confidence
95% confidence
Finding

The reference explicitly states that detected hook files may be added to ~/.claude/settings.json, which is a trusted agent configuration file. Allowing a repository scanner/installer to register hooks into agent config creates a persistence and code-execution path where untrusted repository content can influence future agent behavior beyond the current install session.

Content

Scanner excerpt · REFERENCE.md (reported line 100)May include surrounding context.

md
| `mcp-server.mjs` | MCP | Prints `.mcp.json` config |
| `openclaw.plugin.json` | OpenClaw | Copies to `~/.openclaw/extensions/` |
| `SKILL.md` | Skill | Reports path |
| `guard.mjs` or `claudeCode.hook` | CC Hook | Adds to `~/.claude/settings.json` |

## Real Examples

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The declared description materially understates the installer’s behavior: the finding indicates it can globally install external packages, clone remote repositories, delegate execution to another installer layer, modify multiple user configuration files, alter .gitignore, and delete or migrate existing integrations. This is dangerous because users and policy engines may grant trust based on the benign-sounding description while the actual behavior has broad system, network, and persistence implications that could be abused to run unreviewed code or alter developer environments.

Content

No source excerpt is available for this finding.

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
import { detectInterfaces, describeInterfaces, detectInterfacesJSON } from './detect.mjs';

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
5. **Skill** ... `SKILL.md`

Agent Config Directory Access

High
Category
Agent Snooping
Confidence
90% confidence
Finding

Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.

Content

Scanner excerpt · SPEC.md (reported line 108)May include surrounding context.

Detection: guard.mjs exists, or pkg.claudeCode.hook is defined.

Install: Added to ~/.claude/settings.json under hooks.

json
{

Missing User Warnings

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

The migration routine forcefully deletes extension directories, MCP registrations, skill directories, and registry entries using rm -rf and config rewrites without user confirmation. If matching logic is wrong or manipulated, this can destroy user data and remove unrelated installed tools or agent integrations.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · install.js (reported line 444)May include surrounding context.

js
args: [mcpPath],
      };
      if (existsSync(OC_ROOT)) {
        ocMcp.mcpServers[name].env = { OPENCLAW_HOME: OC_ROOT };
      }
      writeJSON(OC_MCP, ocMcp);
      ok(`MCP (OC): registered ${name} in ${OC_MCP}`);

Agent Config Directory Access

High
Category
Agent Snooping
Confidence
94% confidence
Finding

The skill accesses and modifies agent configuration under ~/.claude/settings.json, a high-sensitivity location controlling persistent Claude Code behavior. In this installer context, that access is especially dangerous because it is used to register hooks that can trigger future command execution.

Content

Scanner excerpt · install.js (reported line 726)May include surrounding context.

js
console.log('    MCP Server ... mcp-server.mjs -> claude mcp add --scope user');
    console.log('    OpenClaw   ... openclaw.plugin.json -> ~/.ldm/extensions/ + ~/.openclaw/extensions/');
    console.log('    Skill      ... SKILL.md -> ~/.openclaw/skills/<tool>/');
    console.log('    CC Hook    ... guard.mjs or claudeCode.hook -> ~/.claude/settings.json');
    console.log('');
    console.log('  Modes:');
    console.log('    Single repo  ... installs one tool');

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The installer documentation describes actions that install packages globally and modify user-level agent configuration locations, but it does not clearly warn users that running the installer may change persistent system or agent settings. In an agent-executed context, this omission is dangerous because users or calling agents may treat detection/install as low-risk and unknowingly permit repository-driven changes to trusted execution surfaces.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
89% confidence
Finding

The skill advertises installation and repository scanning behavior but does not declare any explicit tool scope or allowed tools, despite requiring environment/system capabilities. For an installer that may invoke npm, git, and node and potentially modify user state, missing permission boundaries makes its effective authority ambiguous and increases the risk of unintended or overly broad execution.

Content

No source excerpt is available for this finding.

Session Persistence

Medium
Category
Rogue Agent
Confidence
91% confidence
Finding

Writing MCP server entries into ~/.claude/.mcp.json creates persistent user-scope agent behavior that survives the current session. While persistence is part of installation, it is security-relevant because it causes future executions of repo-derived code from agent tooling without a fresh trust decision.

Content

Scanner excerpt · install.js (reported line 417)May include surrounding context.

js
ok(`MCP (CC): registered ${name} at user scope`);
      ccRegistered = true;
    } catch (e) {
      // Fallback: write to ~/.claude/.mcp.json
      try {
        const mcpConfig = readJSON(ccMcpPath) || { mcpServers: {} };
        mcpConfig.mcpServers[name] = {

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The installer writes command hooks into ~/.claude/settings.json, creating persistent execution of repository-provided commands on future Claude Code events. This is a sensitive user-agent configuration change that can lead to unreviewed code execution well after installation and exceeds a narrow 'repo installer' expectation.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The installer edits the target repository's .gitignore, which is outside the stated purpose of detecting and installing interfaces. Modifying project source trees can create surprising side effects, hide files from version control, and alter developer workflow without consent.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The installer changes .gitignore automatically and without warning, altering repository state in a way users may not notice immediately. Even if the entry seems harmless, unexpected source-tree mutation is unsafe behavior for an installer and can conceal generated worktree artifacts from review.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The installer goes beyond scanning and installing interfaces from the target repository by silently installing and delegating to a separate global package (@wipcomputer/wip-ldm-os). That expands trust to unrelated code, changes the system state globally, and can cause execution paths the user did not request or review.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
99% confidence
Finding

The code silently performs npm install -g @wipcomputer/wip-ldm-os without prior confirmation. Installing global software changes the host environment, extends the trusted codebase, and can execute package lifecycle scripts, making this risky in an installer that users may expect to be limited to the target repo.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The skill manifest says this installer 'scans a repo, detects which interfaces it exposes, and installs them all,' which describes detection and installation of existing interfaces. In package.json, the description instead says it 'teaches your AI how to build repos with every interface,' implying a repo-generation or enablement capability rather than just detection/installation, creating a meaningful intent mismatch.

Content

No source excerpt is available for this finding.

Static analysis

Detected: suspicious.dangerous_exec

Shell command execution detected (child_process).

Critical
Code
suspicious.dangerous_exec
Location
install.js:35