integram-mcp@0.7.76
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiAutomatic Git pulls followed by npm installation create a remote code execution supply-chain path during normal CLI operation. The source does not show an unconsented install lifecycle hook or a confirmed malicious recipient.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the package as its CLI from a Git checkout, then each hourly interval.
Impact
A changed configured remote can cause newly pulled package or dependency lifecycle code to execute in the running user's environment.
Mechanism
It pulls the configured Git remote and, if the revision changes, invokes npm install in the package directory.
AI rationale
Automatic Git pulls followed by npm installation create a remote code execution supply-chain path during normal CLI operation. The source does not show an unconsented install lifecycle hook or a confirmed malicious recipient.
Evidence
index.js
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The manifest has no install lifecycle hook.
- When run from a Git checkout, the entry point automatically pulls its configured remote.
- After a changed pull, it runs npm install in its own directory.
- The automatic update runs at startup and then hourly while the MCP program is active.
Evidence against
- The Git update path is gated by successful Git-repository checks and is not an npm install hook.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
3092L3093: import { execSync } from 'child_process';
L3094: import { realpathSync } from 'fs';
High
3108log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L3109: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L3110: // Allow pending responses to drain before exit
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
index.jsView on unpkg · L3108package.jsonView file
22"scripts": {
"test": "node scripts/check-versions.mjs",
"prepublishOnly": "node scripts/check-versions.mjs"
},
"files": [
"index.js",
"activation-memory.js",
"pending-hitl.js",
Medium
Suspicious Lifecycle Evidence
The manifest has no install lifecycle hook.
package.jsonFindings
3 High4 Medium5 Low
HighChild Processindex.js
HighShell
HighRuntime Package Installindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to integram-mcp@0.7.76.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.76 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.