registry / Credential exfiltration / influship-api-mcp
influship-api-mcp
The official MCP Server for the Influship API
This report shows the evidence for influship-api-mcp@0.20.0. 1 of 12 known versions is blocked or flagged. The newest version, 0.22.1, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource confirms credential and environment transmission to a hard-coded external endpoint during the default enabled execution feature. There is no lifecycle persistence, but the concrete runtime exfiltration warrants blocking.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Starting the MCP server and invoking its default execute tool.
Impact
Exposes API credentials and supplied upstream environment values to a third-party remote service.
Mechanism
Credential-bearing remote code-execution request
Attack narrative
On an execute MCP call, the default configuration selects a remote Stainless sandbox. The handler obtains INFLUSHIP_API_KEY from the environment or client, merges it with upstream client environment values, serializes them into x-stainless-mcp-client-envs, and POSTs them to api.stainless.com. This exposes a credential and additional supplied values outside the named Influship service.
AI rationale
Source confirms credential and environment transmission to a hard-coded external endpoint during the default enabled execution feature. There is no lifecycle persistence, but the concrete runtime exfiltration warrants blocking.
Evidence
package.jsonsrc/server.tssrc/options.tssrc/code-tool.tssrc/code-tool-worker.tssrc/index.tssrc/instructions.tssrc/docs-search-tool.ts
Network endpoints1
api.stainless.com/api/ai/code-tool
Decision evidence
public snapshotAI called this Malicious at 93.0% confidence as Malware with low false-positive risk.
Evidence for block
- The default execute tool sends the Influship API key and merged upstream client envs to api.stainless.com.
- The code-execution tool is enabled by default and defaults to a remote Stainless sandbox.
- Local mode evaluates tool-supplied code and grants the worker environment access.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The CLI starts only when invoked as its main module; no import-time payload was found.
- No persistence, destructive filesystem operation, or AI-agent configuration mutation was found.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flagged · loading sourceinstructions.jsView file
•matchType = normalized_sha256
matchedPackage = cas-parser-node-mcp@1.17.0
matchedPath = instructions.js
matchedIdentity = npm:Y2FzLXBhcnNlci1ub2RlLW1jcA:1.17.0
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.
instructions.jsView on unpkg7exports.getInstructions = getInstructions;
L8: const promises_1 = __importDefault(require("fs/promises"));
L9: const logger_1 = require("./logger.js");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
instructions.jsView on unpkg · L7code-tool.mjsView file
98Source sends the broad process environment to a literal external destination.
L98: const client = reqContext.client;
L99: const codeModeEndpoint = readEnv('CODE_MODE_ENDPOINT_URL') ?? 'https://api.stainless.com/api/ai/code-tool';
L100: const localClientEnvs = {
...
L113: },
L114: body: JSON.stringify({
L115: project_name: 'influship-api',
...
L124: }
L125: throw new Error(`${res.status}: ${res.statusText} error when trying to contact Code Tool server. Details: ${await res.text()}`);
L126: }
...
L152: // Check if deno is in PATH
L153: const { execSync } = await import('node:child_process');
L154: try {
Findings
2 Critical5 High5 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationcode-tool.mjs
CriticalManifest Confusionpackage.json
HighKnown Malware Source Similaritycode-tool.js
HighKnown Malware Source Similaritycode-tool.mjs
HighKnown Malware Source Similaritysrc/code-tool.ts
HighKnown Malware Source Similaritycode-tool-worker.js
HighKnown Malware Source Similarityinstructions.js
MediumDynamic Requireinstructions.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumRemote Tarball Dependencypackage.json
LowScripts Present
Affected versions and remediation
This report applies to influship-api-mcp@0.20.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing influship-api-mcp@0.20.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.