registry / @mnemonik/cli / 7.156.1
@mnemonik/cli@7.156.1
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe scanner flags did not establish malicious behavior: the inspected evaluation matches appear in bundled runtime code, and no package lifecycle scripts are declared. The credential helper's caller, token source, and endpoint configuration remain unresolved, so the source review cannot support a clean or warning verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown; the helper's caller was not established.
Impact
Unresolved; the source reviewed does not show whether a saved credential reaches an unrestricted recipient.
Mechanism
The helper posts a JSON body and bearer token to a server argument.
AI rationale
The scanner flags did not establish malicious behavior: the inspected evaluation matches appear in bundled runtime code, and no package lifecycle scripts are declared. The credential helper's caller, token source, and endpoint configuration remain unresolved, so the source review cannot support a clean or warning verdict.
Decision evidence
public snapshotAI called this Manual Review at 56.0% confidence as Unknown with medium false-positive risk.
AI review observations
- dist/runtime/signers.js defines a helper that sends a bearer token to a server parameter, but the inspected source does not establish its caller, token origin, or endpoint selection.
- package.json has no lifecycle scripts; the CLI entrypoint calls bootstrap when invoked.
Evidence against
- The inspected helper sends a caller-provided body and token to a server argument; the excerpt does not show a fixed recipient or credential harvesting.
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.156.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.156.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.