trace-mcp@1.51.1
Framework-aware code intelligence MCP server — 60 framework integrations, 81 languages, up to 99% token reduction
AI Security Review
scanned 26d ago · by lpm-firewall-aiAutomatic first-party agent-service setup is a lifecycle risk that warrants a warning under the policy. The inspected code does not prove malware or an active exfiltration attack.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
npm installation executes the postinstall hook.
Impact
This creates a durable package-owned local agent service without a separate setup command.
Mechanism
The hook writes launcher configuration, contacts the package release API for an app update, and creates a RunAtLoad and KeepAlive launchd service.
AI rationale
Automatic first-party agent-service setup is a lifecycle risk that warrants a warning under the policy. The inspected code does not prove malware or an active exfiltration attack.
Evidence
~/.trace-mcp/launcher.env~/.trace-mcp/bin/trace-mcp~/Library/LaunchAgents/com.trace-mcp.server.plist
Network endpoints1
api.github.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs three scripts automatically in a postinstall hook.
- The postinstall app updater queries the package release endpoint.
- The control-plane postinstall writes a launcher environment file and creates a persistent launchd service configuration.
Evidence against
- The observed network request targets the package's GitHub release API.
- The inspected updater requires a checksum asset before proceeding; no credential collection or exfiltration was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNativeBindingsNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/preflight-native.mjs && node scripts/postinstall-app.mjs && node scripts/postinstall-control-plane.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/preflight-native.mjs && node scripts/postinstall-app.mjs && node scripts/postinstall-control-plane.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/postinstall-app.mjsView file
17* not destroy the working installation.
L18: * - `unzip` is invoked with execFileSync (no shell) to avoid argument
L19: * injection via asset names.
...
L23:
L24: import { execFileSync } from 'node:child_process';
L25: import crypto from 'node:crypto';
L26: import fs from 'node:fs';
L27: import http from 'node:http';
L28: import https from 'node:https';
...
L49:
L50: if (process.env.TRACE_MCP_NO_AUTO_UPDATE === '1') process.exit(0);
L51:
Findings
5 High8 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilityscripts/postinstall-app.mjs
HighSemantic Analysis Limitedscripts/calibrate-health-metrics.mjs#virtual:normalized:round1
HighKnown Malware Source Similarityscripts/bench-toon.ts
HighPrevious Version Dangerous Deltascripts/postinstall-app.mjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Require
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperhooks/trace-mcp-reindex.sh
MediumOversized Source Filedist/index.js
MediumOversized Cli Entrypointdist/cli.js
Affected versions and remediation
This report applies to trace-mcp@1.51.1.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@1.51.1 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.