registry / @cachly-dev/mcp-server / 0.10.196
@cachly-dev/mcp-server@0.10.196
Solve it once. From then on, your AI knows. Experience for coding agents, EU-hosted: an MCP server for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, commit and CI run.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe runtime credential-recovery path can change user-level agent configuration, which fits the warning boundary for first-party setup. The inspected source shows no install-time config mutation or broader agent-control attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A tool request reaches authentication with no API key loaded and a saved Cachly credential is found.
Impact
This changes user-level agent configuration and makes the Cachly server available in Claude; the inspected path is limited to the package’s own entry.
Mechanism
The recovery path writes the credential into the Cachly entry in the user’s Claude MCP config. It updates Cursor and Windsurf configs only when they already contain a Cachly entry.
AI rationale
The runtime credential-recovery path can change user-level agent configuration, which fits the warning boundary for first-party setup. The inspected source shows no install-time config mutation or broader agent-control attack.
Evidence
dist/src/index.jsdist/src/credentials.js.claude/mcp.json.cursor/mcp.json.codeium/windsurf/mcp_config.json
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When a tool request has no loaded API key, the authentication path checks for a saved credential and invokes the config persistence helper.
- That helper adds or updates the package’s own Cachly entry in the user’s Claude MCP config; it updates Cursor and Windsurf configs only when they already contain a Cachly entry.
- The npm postinstall prints a suggestion to run the separate autopilot command; the inspected postinstall does not perform the config write.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
18 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/src/autor.jsView file
1import{execFileSync as c}from"node:child_process";const f=e=>n=>{try{return n.startsWith("-")?"":c("git",["config",n],{cwd:e,encoding:"utf-8",stdio:"pipe",timeout:1500,windowsHide:...
High
Findings
2 Critical13 High5 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationdist/src/index.js
CriticalPrevious Version Dangerous Deltadist/src/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/src/autor.js
HighSame File Env Network Executiondist/src/index.js
HighCredential Exfiltrationdist/src/index.js
HighTrigger Reachable Credential Exfiltrationdist/src/index.js
HighRuntime Package Installdist/src/cls-hook.js
HighSemantic Analysis Limiteddist/src/doctor.js#virtual:normalized:round1
HighKnown Malware Source Similaritydist/src/index.js
HighKnown Malware Source Similarityhooks/cachly-ambient-einblendung.mjs
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.196.
See all versions of @cachly-dev/mcp-server for other recorded verdicts.
- Review the evidence and your use of @cachly-dev/mcp-server@0.10.196 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.