registry  /  peaks-loop  /  3.0.2

peaks-loop@3.0.2

Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration

AI Security Review

scanned 1d ago · by lpm-firewall-ai

The package mutates AI-agent control surfaces during npm lifecycle installation. The behavior is disclosed in docs and aligned with the package's AI workflow-tool purpose, but it is still unconsented install-time agent/skill deployment across user home IDE directories.

Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install/npm install -g runs postinstall
Impact
Package-supplied prompts/agents can influence future AI assistant behavior in supported IDEs
Mechanism
lifecycle AI-agent skill/agent installation
Attack narrative
On package installation, npm runs scripts/install-skills.mjs. That script resolves user-home AI IDE directories and installs bundled skills, output styles, and agents into them, including Claude/Codex/Cursor/Trae-style control surfaces. These files can later steer AI agent workflows without the user invoking the peaks CLI at that moment.
Rationale
Source inspection confirms concrete install-time AI-agent control-surface mutation via package lifecycle, which LPM policy treats as blockable even though it is package-aligned and lacks exfiltration. Other high-risk primitives reviewed appear user-invoked CLI functionality rather than hidden malware. Product guard normalized a non-low false-positive publish_block request to warn-only suspicious.
Evidence
package.jsonscripts/install-skills.mjsagents/karpathy-reviewer.mdskills/peaks-solo/SKILL.mdskills/peaks-ui/SKILL.mddist/src/shared/process.jsdist/src/services/upgrade/upgrade-service.js~/.claude/skills~/.claude/output-styles~/.claude/agents~/.codex/skills~/.codex/output-styles~/.codex/agents~/.cursor/skills~/.cursor/output-styles~/.trae/skills~/.trae/output-styles

Decision evidence

public snapshot
AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for block
  • package.json postinstall runs scripts/install-skills.mjs on install
  • scripts/install-skills.mjs installs package-supplied skills/output-styles/agents into ~/.claude, ~/.codex, ~/.cursor, ~/.trae, ~/.qoder, etc.
  • scripts/install-skills.mjs has explicit policy goal: npm install -g should symlink skills to every supported AI IDE
  • agents/karpathy-reviewer.md says postinstall copies it to ~/.claude/agents/karpathy-reviewer.md on every install
  • Bundled skills contain agent workflow instructions that change AI assistant behavior, not just passive library data
Evidence against
  • Install script uses marker files, symlink/copy checks, path validation, and atomic writes
  • No credential exfiltration or remote payload download found in inspected install script
  • Network URLs observed are repository/readme/registry/localhost documentation links, not exfiltration endpoints
  • Child_process usage in dist appears tied to user-invoked CLI/audit/git workflows
Behavioral surface
Source
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemShell
Supply chain
HighEntropyStringsUrlStrings
ManifestNo manifest risk signals triggered.
scanned 443 file(s), 2.89 MB of source, external domains: api.anthropic.com, api.example.com, api.openai.com, github.com, gitlab.com, reactbits.dev, www.google.com, www.pulsemcp.com

Source & flagged code

6 flagged · loading source
package.jsonView file
scripts.postinstall = node ./scripts/install-skills.mjs
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
dist/src/shared/process.jsView file
1import { execFile } from 'node:child_process'; L2: export async function execCommand(command, args, options) {
High
Child Process

Package source references child process execution.

dist/src/shared/process.jsView on unpkg · L1
dist/src/services/upgrade/upgrade-service.jsView file
151// npm install postinstall creates `peaks` → `peaks.sh` on L152: // Windows). cmd.exe (the default Windows shell) cannot run L153: // `.sh` scripts directly, so the shim fails with "unknown
High
Shell

Package source references shell execution.

dist/src/services/upgrade/upgrade-service.jsView on unpkg · L151
dist/src/cli/commands/loop-eval-commands.jsView file
478// eslint-disable-next-line @typescript-eslint/no-var-requires L479: const fs = require('node:fs'); L480: let entries;
Medium
Dynamic Require

Package source references dynamic require/import behavior.

dist/src/cli/commands/loop-eval-commands.jsView on unpkg · L478
scripts/install-skills.mjsView file
1Install-time AI-agent control hijack evidence: L1: #!/usr/bin/env node L2: import { closeSync, constants, existsSync, fchmodSync, fstatSync, lstatSync, mkdirSync, openSync, readFileSync, readlinkSync, realpathSync, readdirSync, renameSync, symlinkSync, un... L3: import { spawnSync } from 'node:child_process'; ... L291: fchmodSync(fd, 0o600); L292: writeFileSync(fd, content, 'utf8'); L293: const writeFd = fd; ... L320: fchmodSync(fd, 0o600); L321: writeFileSync(fd, content, 'utf8'); L322: const writeFd = fd; ... L372: * cannot import the TS service at runtime. The dispatch: L373: * - Look for `.claude`, `.trae`, `.codex`, `.cursor`, `.qoder`, L374: * `.tongyi-lingma` in the project root in that insertion order Payload evidence from schemas/mcp-install-spec.schema.json: L1: { L2: "$schema": "https://json-schema.org/draft/2020-12/schema", L3: "title": "Peaks MCP Install Spec", ... L25: "items": { "type": "string" }, L26: "description": "Required env var names. Values are sourced from process.env at runtime and written as ${VAR} placeholders into settings.json." L27: }
Critical
Ai Agent Control Hijack

Install-time source drops package-supplied AI-agent/MCP control files or instructions.

scripts/install-skills.mjsView on unpkg · L1
dist/src/cli/commands/playwright-commands.jsView file
27* The CLI does NOT bundle `playwright-mcp`; it shells out to L28: * `npx playwright-mcp@latest` (G22 / NG3). peaks-loop is the lifecycle L29: * orchestrator, not the install medium. ... L31: import { createHash } from 'node:crypto'; L32: import { spawn } from 'node:child_process'; L33: import { existsSync, mkdirSync, readFileSync, writeFileSync, readdirSync, unlinkSync } from 'node:fs';
High
Runtime Package Install

Package source invokes a package manager install command at runtime.

dist/src/cli/commands/playwright-commands.jsView on unpkg · L27

Findings

1 Critical4 High3 Medium5 Low
CriticalAi Agent Control Hijackscripts/install-skills.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/src/shared/process.js
HighShelldist/src/services/upgrade/upgrade-service.js
HighRuntime Package Installdist/src/cli/commands/playwright-commands.js
MediumDynamic Requiredist/src/cli/commands/loop-eval-commands.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings