registry / @mnemonik/cli / 7.163.1
@mnemonik/cli@7.163.1
Mnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest declares no lifecycle scripts, and the inspected source ties the flagged evaluation and process execution to scanner and permission-check functionality. Network behavior observed in the reviewed paths is associated with the Mnemonik installation workflow or caller-supplied request parameters; no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI runs when a user invokes it; install reporting occurs during its installation flow.
Impact
No confirmed credential theft, unrelated data transfer, persistence, or unconsented install-time mutation was established.
Mechanism
The scanner builds JavaScript glue from WebAssembly data, diagnostics runs permission-check commands, and authenticated requests use supplied server and token values or the Mnemonik API.
AI rationale
The manifest declares no lifecycle scripts, and the inspected source ties the flagged evaluation and process execution to scanner and permission-check functionality. Network behavior observed in the reviewed paths is associated with the Mnemonik installation workflow or caller-supplied request parameters; no concrete attack behavior was established.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts; execution begins through the CLI entry point and its bootstrap.
- The reported eval calls construct JavaScript glue from WebAssembly module data in the scanner and diagnostics bundles; they do not establish execution of code from a remote response.
- The hook helper posts a context body to its supplied server using its supplied token. The body contains project and repository context hashes, while installer readiness reporting uses the Mnemonik API.
Evidence against
- The bundles contain dynamic evaluation and child-process calls, but the inspected contexts show WebAssembly glue generation and Windows permission checks.
- The installer contacts the Mnemonik API during its install flow, and the hook helper can make authenticated requests; inspected source does not show hidden credential harvesting or an unrelated recipient.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystem
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.163.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.163.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.