@mnemonik/cli@7.139.9
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThis is a conditional credential exposure risk, not evidence of covert theft or malicious intent. The user-invoked trigger and configurable destination warrant a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes hook setup when no reusable hook credential is stored.
Impact
If that origin points to an unrelated host, the host receives the bearer token.
Mechanism
The CLI sends its bearer token to the configured API origin without restricting the destination host.
AI rationale
This is a conditional credential exposure risk, not evidence of covert theft or malicious intent. The user-invoked trigger and configurable destination warrant a warning.
Evidence
dist/install/hosts.jsdist/auth/status.jsdist/auth/installSession.js
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest has no install lifecycle scripts, so the credential transfer is not triggered by package installation.
- During hook setup, the CLI obtains its existing bearer token and sends it in a request for component credentials.
- The request destination uses a configurable API origin with no host restriction; the default is the Mnemonik API.
- Other authenticated API requests also use that configured origin, consistent with a configurable API client.
Evidence against
- The transfer is conditional on user-invoked hook setup and an absent stored hook credential.
- The source does not establish that the default Mnemonik API is unrelated or that the token is sent there covertly.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/diagnostics.jsView file
898import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L899: import { execFile, execFileSync } from "node:child_process";
L900: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L8985213var func = `(${args}) => { ${body} };`;
L5214: ASM_CONSTS[start] = eval(func);
L5215: }
High
1import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
L2: var __create = Object.create;
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/diagnostics.jsView on unpkg · L1Findings
1 Critical5 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.js
HighChild Processdist/diagnostics.js
HighEvaldist/diagnostics.js
HighSame File Env Network Executiondist/install/journey.js
HighSandbox Evasion Gated Capabilitydist/install/journey.js
HighCross File Remote Execution Contextdist/auth/credentials.js
MediumDynamic Requiredist/diagnostics.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @mnemonik/cli@7.139.9.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.9 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.