registry / @mnemonik/cli / 7.154.1
@mnemonik/cli@7.154.1
Mnemonik installer and local project helper
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no install hook and no concrete malicious behavior. Scanner hits for eval, process execution, and networking are explained by bundled assembly glue and product-aligned CLI operations.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI or invoking its update, scanner, installer, or diagnostics features.
Impact
No malicious effect was established from the inspected source.
Mechanism
The CLI performs product management tasks; the reviewed update flow fetches release metadata from the npm registry and validates the package and signed release manifest.
AI rationale
Source inspection found no install hook and no concrete malicious behavior. Scanner hits for eval, process execution, and networking are explained by bundled assembly glue and product-aligned CLI operations.
Network endpoints1
registry.npmjs.org/%40mnemonik%2Fcli/
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts or runtime dependencies.
- The eval matches occur in bundled assembly glue that builds functions from module data; no remote response is shown feeding those sinks.
- The updater targets the npm registry, checks package identity and integrity, and validates a signed release manifest.
- The hook request helper sends its supplied token to its supplied server; source inspection did not find a hidden fixed recipient.
- The inspected scanner, installer, and diagnostics code performs product management tasks; no concrete attack behavior was established.
Evidence against
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 · L9235257var func = `(${args}) => { ${body} };`;
L5258: ASM_CONSTS[start] = eval(func);
L5259: }
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.154.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.154.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.