@roarkanalytics/sdk-mcp@3.14.3
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe credential-forwarding path is real in shipped runtime code, but it is not active through the normal CLI default and is plausibly a legacy remote-execution integration. This leaves a material, reachable credential-exposure risk rather than sufficient evidence of unequivocal malicious intent.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
An MCP execute request after a consumer initializes the library without explicit code-execution options.
Impact
A third-party endpoint can receive a Roark API bearer token, base URL, and supplied client environment values.
Mechanism
Remote forwarding of bearer-token-derived client environment values.
AI rationale
The credential-forwarding path is real in shipped runtime code, but it is not active through the normal CLI default and is plausibly a legacy remote-execution integration. This leaves a material, reachable credential-exposure risk rather than sufficient evidence of unequivocal malicious intent.
Evidence
server.jscode-tool.jscode-tool.mjssrc/code-tool.ts
Network endpoints1
api.stainless.com/api/ai/code-tool
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The library API defaults its code tool to the remote Stainless sandbox when no options are supplied.
- That remote handler collects the Roark bearer token and base URL, merges supplied client environment values, and posts them to api.stainless.com.
- The shipped CommonJS and ESM runtime files contain the same credential-forwarding handler.
Evidence against
- The CLI defaults to local execution and explicitly rejects the retired remote sandbox mode.
- There are no npm install lifecycle hooks or automatic project-file mutations.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 flagged · loading sourceinstructions.jsView file
•matchType = normalized_sha256
matchedPackage = @roarkanalytics/sdk-mcp@3.12.1
matchedPath = instructions.js
matchedIdentity = npm:QHJvYXJrYW5hbHl0aWNzL3Nkay1tY3A:3.12.1
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.jsView file
52Source sends the broad process environment to a literal external destination.
L52: interfaceType: 'PHONE',
L53: recordingUrl: 'https://example.com',
L54: startedAt: 'startedAt',
...
L155: },
L156: body: JSON.stringify({
L157: project_name: 'roark-analytics',
...
L166: }
L167: throw new Error(`${res.status}: ${res.statusText} error when trying to contact Code Tool server. Details: ${await res.text()}`);
L168: }
...
L214: // Check if deno is in PATH
L215: const { execSync, spawn } = await Promise.resolve().then(() => __importStar(require('node:child_process')));
L216: try {
Findings
2 Critical7 High5 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationcode-tool.js
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedcode-tool.js#virtual:normalized:round1
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
HighKnown Malware Source Similaritylocal-docs-search.js
MediumDynamic Requireinstructions.js
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @roarkanalytics/sdk-mcp@3.14.3.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.14.3 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.