mano-coding@0.1.35
Mano Coding CLI and toolchain
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a user-invoked extension manager with a meaningful remote command-execution capability, not evidence of an install-time malware chain. The static eval and shell alerts do not establish malicious execution, but remote task execution merits a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs create, apply, sync, or another extension operation that executes tasks.
Impact
A compromised or untrusted extension registry entry can cause commands to run within the selected project directory.
Mechanism
Remote manifest task commands are interpolated and launched as child processes.
AI rationale
This is a user-invoked extension manager with a meaningful remote command-execution capability, not evidence of an install-time malware chain. The static eval and shell alerts do not establish malicious execution, but remote task execution merits a warning.
Evidence
dist/bin.js
Network endpoints1
git.iec.io/farris-public/extension-registry
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package exposes a command-line tool that runs only when the user invokes its bin command.
- The CLI obtains extension registry data from a configured remote registry.
- Remote task fields supply a command and arguments that the CLI launches as a child process.
- This creates a user-triggered remote extension command-execution capability in a consumer project.
Evidence against
- The manifest has no preinstall, install, or postinstall lifecycle hook.
- The bundled command runner uses shell disabled and restricts task working directories.
- No secret harvesting, outbound upload of command output, stealth persistence, or self-dependency was found.
- The reported eval reference is Ajv schema-validator code generation, not remote response evaluation.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
7 flaggeddist/bin.jsView file
49* Constructs the CommanderError class
L50: * @param {number} exitCode suggested exit code which could be used with process.exit
L51: * @param {string} code an id string representing the error
...
L1159: var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path2 = __require("node:path");
...
L1209: this._outputConfiguration = {
L1210: writeOut: (str) => process4.stdout.write(str),
L1211: writeErr: (str) => process4.stderr.write(str),
...
L1248: * @returns {Command[]}
L1249: * @private
L1250: */
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/bin.jsView on unpkg · L491159var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path2 = __require("node:path");
High
1999}
L2000: const execArgv = process4.execArgv ?? [];
L2001: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) {
High
Findings
1 Critical5 High4 Medium5 Low
CriticalRemote Response Code Executiondist/bin.js
HighChild Processdist/bin.js
HighShelldist/bin.js
HighEvaldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighCommand Output Exfiltrationdist/bin.js
MediumDynamic Requirebin/mano-coding.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to mano-coding@0.1.35.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.35 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.