registry / @mnemonik/cli / 7.159.0
@mnemonik/cli@7.159.0
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, but an inspected runtime helper sends a bearer token to a server parameter. Its source, destination selection, and caller consent could not be resolved, so the package’s risk remains undetermined.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown from the inspected excerpts; the helper’s activation path was not established.
Impact
Potential credential exposure cannot be determined without tracing the token source, recipient, and callers.
Mechanism
The helper posts a JSON body with a bearer token to a server argument.
AI rationale
The manifest has no lifecycle scripts, but an inspected runtime helper sends a bearer token to a server parameter. Its source, destination selection, and caller consent could not be resolved, so the package’s risk remains undetermined.
Evidence
dist/runtime/signers.js
Decision evidence
public snapshotAI called this Manual Review at 68.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares no lifecycle scripts and points to a CLI binary and runtime entrypoint.
- dist/runtime/signers.js contains a helper that sends a bearer token to a server argument, but the inspected excerpt does not establish the token’s origin, the server’s value, or the callers’ consent guards.
Evidence against
- The inspected package entrypoint invokes the CLI bootstrap when the binary is run; this alone does not establish an attack.
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.159.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.159.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.