chat-recall@0.6.3
Shared team knowledge, leaked-secret alerts, ranked code findings and tracked tasks, across every AI coding tool you use
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no install lifecycle hook, but its automatic updater creates a concrete remote code execution path from a configured sync server. This is a critical supply-chain vulnerability; static source alone does not establish malicious author intent.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A successful sync response advertising a newer CLI version.
Impact
A compromised or malicious configured server can achieve code execution as the user and replace the CLI.
Mechanism
Server-directed archive download followed by global npm installation.
AI rationale
The package has no install lifecycle hook, but its automatic updater creates a concrete remote code execution path from a configured sync server. This is a critical supply-chain vulnerability; static source alone does not establish malicious author intent.
Evidence
dist/sync-client.jsdist/auto-update.jspackage.json
Network endpoints3
chatrecall.dev<configured-server>/api/sync<configured-server>/api/capabilities
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- A successful sync response can automatically start a self-update.
- The update decision accepts both version and checksum from the configured server.
- The downloaded archive is installed globally with npm and the watch service may be restarted.
- This permits a configured or compromised server to replace the locally running CLI.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The update path is reached during a user-configured sync, not package installation.
- Sync credentials are stored only after login and use restrictive file permissions.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
WildcardDependency
Source & flagged code
20 flaggeddist/self-restart.jsView file
40*/
L41: import { spawn } from 'child_process';
L42: import { readFileSync } from 'fs';
High
Child Process
Package source references child process execution.
dist/self-restart.jsView on unpkg · L40dist/watch.jsView file
12522try {
L12523: const out2 = execFileSync2("powershell", [
L12524: "-NoProfile",
High
1200for (var i = 0; i < flen; ) {
L1201: if (f.charCodeAt(i) === 37 && i + 1 < flen) {
L1202: lastPos = lastPos > -1 ? lastPos : 0;
...
L1435: fsWriteSync = () => fs.writeSync(this.fd, this._writingBuf);
L1436: fsWrite = () => fs.write(this.fd, this._writingBuf, this.release);
L1437: } else if (contentMode === void 0 || contentMode === kContentModeUtf8) {
...
L2000:
L2001: // ../../node_modules/thread-stream/package.json
L2002: var require_package = __commonJS({
...
L2045: type: "git",
L2046: url: "git+https://github.com/mcollina/thread-stream.git"
L2047: },
Findings
3 Critical13 High7 Medium5 Low
CriticalCredential Exfiltrationdist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
CriticalPrevious Version Dangerous Deltadist/service-installer.js
HighChild Processdist/self-restart.js
HighShelldist/watch.js
HighSame File Env Network Executiondist/mcp.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/watch.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighRemote Agent Bridgedist/mcp.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/cli.js
High
Affected versions and remediation
This report applies to chat-recall@0.6.3.
See all versions of chat-recall for other recorded verdicts.
- Review the evidence and your use of chat-recall@0.6.3 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.