@cachly-dev/mcp-server@0.10.208
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 6d ago · by lpm-firewall-aiThe configurable API base is unrestricted, and the shared request wrapper sends locally resolved tokens to it. Because the default destination is package-aligned and exposure depends on a custom endpoint setting, this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The server starts with an existing token and makes an API request while CACHLY_API_URL points to a custom host.
Impact
The selected host receives the token, creating conditional credential exposure.
Mechanism
The server loads the token from environment or local configuration, then adds it to requests formed with the configurable API base.
AI rationale
The configurable API base is unrestricted, and the shared request wrapper sends locally resolved tokens to it. Because the default destination is package-aligned and exposure depends on a custom endpoint setting, this warrants a warning rather than a block.
Evidence
dist/src/index.jsdist/src/credentials.js
Network endpoints1
api.cachly.dev
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- dist/src/index.js defaults the API base to https://api.cachly.dev but allows CACHLY_API_URL to replace it.
- The server resolves its bearer token from CACHLY_JWT, CACHLY_API_KEY, saved credentials, or the project MCP config.
- The shared API wrapper sends that token as a bearer credential to the configured base without a host restriction.
- The instance failure telemetry request also attaches the token to that configurable base.
- The Redis failure telemetry request also attaches the token to that configurable base.
- package.json invokes a postinstall script that prints an explicit setup command; that script does not initiate this credential transfer.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
15 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
1 Critical11 High5 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationdist/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 Similarityhooks/cachly-ambient-einblendung.mjs
HighKnown Malware Source Similaritydist/src/handlers/cache.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.208.
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.208 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.