registry / @mnemonik/cli / 7.157.6
@mnemonik/cli@7.157.6
Mnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe package has no install lifecycle script, and the reviewed credential helper has no identified package caller that supplies saved credentials or an unrelated destination. The static indicators alone do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The helper runs only when called; the CLI entrypoint invokes its runtime bootstrap when the executable is run.
Impact
No automatic collection or transfer of saved credentials was established.
Mechanism
The helper forms a POST URL from its server and path arguments, sets a bearer authorization header from its token argument, and serializes its body argument.
AI rationale
The package has no install lifecycle script, and the reviewed credential helper has no identified package caller that supplies saved credentials or an unrelated destination. The static indicators alone do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 76.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts and exposes the CLI through dist/bin.js; the executable invokes bootstrap when run.
- The credential-bearing POST helper accepts its server, path, token, and body as arguments; the body is serialized directly, and package search found no callers of the helper.
- The inspected package entrypoints and runtime source did not establish automatic credential forwarding or another concrete attack.
Evidence against
- The exported helper can send a bearer token to its supplied server, so callers must control the destination and token appropriately.
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.157.6.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.157.6 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.