@mnemonik/cli@7.173.3
Mnemonik installer and local project helper
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe installer sends project-identifying fields, including owner and identity-file name, to the package’s service without a visible opt-out in the reviewed flow. This is suspicious telemetry, but the transfer occurs in the user-run setup workflow and does not establish malicious credential theft.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the CLI installer and it reaches its completion report; sending requires an available CLI bearer.
Impact
Project-identifying metadata is disclosed to the package’s service. No third-party credential transfer was identified.
Mechanism
The workflow serializes readiness data, which can include project identifiers and names, then posts it to the Mnemonik API.
AI rationale
The installer sends project-identifying fields, including owner and identity-file name, to the package’s service without a visible opt-out in the reviewed flow. This is suspicious telemetry, but the transfer occurs in the user-run setup workflow and does not establish malicious credential theft.
Evidence
dist/install/journey.js
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When installation completes, the workflow uses a CLI bearer to send a readiness report to the Mnemonik API; the default host is api.mnemonik.dev.
- The readiness report can include project ID, display name, owner, repository match, and identity-file name.
Evidence against
- The package has no lifecycle scripts, and its manifest lists no runtime dependencies.
- The report is part of the CLI installation workflow and goes to the package’s own service; I found no transfer of third-party credentials.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 flaggeddist/diagnostics.jsView file
923import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L924: import { execFile, execFileSync } from "node:child_process";
L925: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9235256var func = `(${args}) => { ${body} };`;
L5257: ASM_CONSTS[start] = eval(func);
L5258: }
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 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/scanner/service.js
HighChild Processdist/diagnostics.js
HighEvaldist/diagnostics.js
HighSame File Env Network Executiondist/install/journey.js
HighCommand Output Exfiltrationdist/runtime/signers.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
Affected versions and remediation
This report applies to @mnemonik/cli@7.173.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.173.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.