registry / @mnemonik/cli / 7.156.4
@mnemonik/cli@7.156.4
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe package manifest has no install lifecycle scripts, and its executable enters the CLI bootstrap. The inspected request helper exposes an unresolved credential-transfer path, so the available source does not support either a clean verdict or a confirmed attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Unresolved; the inspected CLI entrypoint runs bootstrap, but the connection between that path and the request helper was not established.
Impact
The excerpts do not establish whether credentials or sensitive data reach an unrelated recipient.
Mechanism
The helper posts JSON to a URL formed from its server argument and adds its token argument as a bearer authorization header.
AI rationale
The package manifest has no install lifecycle scripts, and its executable enters the CLI bootstrap. The inspected request helper exposes an unresolved credential-transfer path, so the available source does not support either a clean verdict or a confirmed attack.
Decision evidence
public snapshotAI called this Manual Review at 48.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines the CLI entrypoints and has no lifecycle scripts or runtime dependencies.
- The CLI entrypoint invokes bootstrap when run.
- The request helper sends a bearer token and JSON body to a server argument, but the inspected source does not establish who supplies the token or server, or which caller activates this helper.
Evidence against
- The helper uses its server argument to construct the request destination; these excerpts do not show a package-selected default recipient.
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.4.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.156.4 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.