registry / claude-code-infinite / 1.0.28
claude-code-infinite@1.0.28
Wrapper for Claude Code CLI
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found product-aligned CLI and MemTree behavior, with no install-time hook or confirmed attack path. The scanner’s download-and-execute hint was not borne out by the inspected claude-locate source.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The package CLI runs when invoked; the package build hook runs before publication.
Impact
No confirmed attack impact was identified.
Mechanism
The reviewed code launches Claude through the local proxy, resolves local Claude installations, and formats MemTree results. No malicious payload execution or unauthorized credential transfer was established.
AI rationale
Source inspection found product-aligned CLI and MemTree behavior, with no install-time hook or confirmed attack path. The scanner’s download-and-execute hint was not borne out by the inspected claude-locate source.
Evidence
package.jsondist/cli-main.jsdist/claude-locate.jsdist/memtree-tools.js
Network endpoints1
polychat.co
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and a prepublish build hook; the dependency manifest has no install lifecycle hook.
- The inspected cross-spawn entrypoint parses a requested command and spawns it as a child process.
- The six flagged memtree-tools locations format search results, matched paths, and transcript snippets.
- The inspected request and authentication code classifies Claude request metadata and login type; hook code defines display notices.
- The launcher imports its local proxy and CLI helpers; claude-locate resolves local Claude paths and checks Windows registry PATH values.
- The inspected fetch command avoids sending a key to non-Polychat hosts; project-tree lookup and transcript repair are bounded product functions.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/resume-repair-file.jsView file
4import { randomUUID } from "node:crypto";
L5: import { execFileSync } from "node:child_process";
L6: /** Possible writers include Claude binaries and JS runtimes; uncertainty skips repair. */
High
Child Process
Package source references child process execution.
dist/resume-repair-file.jsView on unpkg · L4dist/cli-main.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = claude-code-infinite@1.0.27
matchedIdentity = npm:Y2xhdWRlLWNvZGUtaW5maW5pdGU:1.0.27
similarity = 0.868
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli-main.jsView on unpkg71platform === "win32"
L72: ? exec(`${command} "${url}"`, { shell: "cmd.exe" })
L73: : exec(`${command} "${url}"`);
Findings
3 Critical4 High3 Medium5 Low
CriticalDownload Executedist/claude-locate.js#virtual:normalized:round1
CriticalTrigger Reachable Dangerous Capabilitydist/claude-locate.js#virtual:normalized:round1
CriticalPrevious Version Dangerous Deltadist/cli-main.js
HighChild Processdist/resume-repair-file.js
HighShelldist/cli-main.js
HighSame File Env Network Executiondist/cli-main.js
HighSemantic Analysis Limiteddist/cc-request.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to claude-code-infinite@1.0.28.
See all versions of claude-code-infinite for other recorded verdicts.
- Review the evidence and your use of claude-code-infinite@1.0.28 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.