registry / @mnemonik/cli / 7.158.0
@mnemonik/cli@7.158.0
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the scanner's inspected `eval` use belongs to its WebAssembly support. I could not resolve the hook token's callers and destination controls from the inspected excerpts, so the credential flow remains undetermined.
Static reason
One or more suspicious static signals were detected.
Trigger
A runtime hook request, if a caller invokes the helper.
Impact
The token could be disclosed if a caller supplies an unrelated destination, but that behavior was not confirmed.
Mechanism
The helper posts JSON and a bearer token to a server parameter supplied by its caller; source reviewed here does not establish that parameter's origin or safeguards.
AI rationale
The manifest has no lifecycle scripts, and the scanner's inspected `eval` use belongs to its WebAssembly support. I could not resolve the hook token's callers and destination controls from the inspected excerpts, so the credential flow remains undetermined.
Decision evidence
public snapshotAI called this Manual Review at 65.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines no lifecycle scripts.
- The CLI invokes its bootstrap when run; the inspected bootstrap entry validates the installed package path and lockfile.
- The scanner `eval` calls build functions from embedded WebAssembly exports; the inspected language loader accepts a supplied byte buffer or file path.
- A hook helper sends a bearer token to a caller-supplied server, but the relevant callers and effective destination controls remain unresolved.
Evidence against
- No confirmed attack behavior was established in the inspected source excerpts.
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.158.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.158.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.