registry / @mnemonik/cli / 7.152.0
@mnemonik/cli@7.152.0
Mnemonik installer and local project helper
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. Inspected source explains the eval and update signals as WebAssembly support and integrity-checked self-updating; the hook request remains insufficiently traced to establish an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI invokes its bootstrap; update checks and hook requests occur through runtime operations.
Impact
No confirmed attack impact was established from the inspected behavior.
Mechanism
The inspected update path obtains Mnemonik CLI release metadata from the npm registry and checks identity and integrity against a signed manifest. A hook helper can POST JSON to a supplied server, but its callers and effective destination controls were not resolved.
AI rationale
The manifest has no install lifecycle hook. Inspected source explains the eval and update signals as WebAssembly support and integrity-checked self-updating; the hook request remains insufficiently traced to establish an attack.
Evidence
package.jsondist/runtime/selfUpdate.jsdist/runtime/signers.js
Network endpoints1
registry.npmjs.org/%40mnemonik%2Fcli/
Decision evidence
public snapshotAI called this Clean at 78.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts and exposes the CLI through dist/bin.js.
- The flagged eval calls compile JavaScript embedded in WebAssembly module exports; the inspected context does not show remote response text reaching eval.
- The self-update path uses the Mnemonik npm registry and checks release identity, integrity, and a signed manifest before installing an update.
Evidence against
- The CLI contains a hook helper that sends JSON with a bearer token to a supplied server; the inspected excerpt does not establish its callers, destination selection, or consent boundary.
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 · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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/runtime/selfUpdate.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.152.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.152.0 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.