registry / integram-mcp / 0.7.161
integram-mcp@0.7.161
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe static source does not establish malware, and the npm manifest has no install lifecycle hook. The unprompted Git pull and dependency installation in checkout mode leave a real unattended update risk, so this warrants a warning.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Starting the CLI, then each hourly update check, when the package directory is a Git checkout.
Impact
Remote source and dependency changes may be installed and run by the host after restart. The inspected source does not establish a malicious payload or intent.
Mechanism
The updater pulls from the checkout's configured Git remote; when the commit changes, it runs npm install and schedules a process exit for restart, without asking for approval.
AI rationale
The static source does not establish malware, and the npm manifest has no install lifecycle hook. The unprompted Git pull and dependency installation in checkout mode leave a real unattended update risk, so this warrants a warning.
Evidence
index.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI entrypoint has only test and prepublishOnly scripts; no npm install lifecycle hook is declared.
- The entrypoint runs a Git self-update on startup and hourly. When the checkout changes, it runs npm install and exits so the host can restart it.
- The updater runs Git checks inside a catch block, so directories that are not Git checkouts skip the update path; the update itself has no user-approval gate.
- Authenticated startup checks notification summaries and formats them for display; no account-changing action was identified in this path.
Evidence against
- In a Git checkout, the updater automatically pulls from its configured remote and installs dependencies after a change, creating an unattended code and dependency update path.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flagged · loading sourceindex.jsView file
2384L2385: import { execSync } from 'child_process';
L2386: import { realpathSync } from 'fs';
High
2412log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L2413: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L2414: // 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 · L2412•matchType = normalized_sha256
matchedPackage = integram-mcp@0.7.160
matchedPath = index.js
matchedIdentity = npm:aW50ZWdyYW0tbWNw:0.7.160
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
index.jsView on unpkgFindings
5 High3 Medium5 Low
HighChild Processindex.js
HighShell
HighRuntime Package Installindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to integram-mcp@0.7.161.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.161 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.