@kerno/cli@0.2.1
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no automatic remote execution at install time, but its explicit agent setup executes an unverified remote script. This is a concrete remote-code-execution capability rather than confirmed malware.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs kerno init and the agent needs installation or update.
Impact
A change to the remotely hosted installer can execute commands with the invoking user's permissions.
Mechanism
The CLI retrieves a versioned script from raw.githubusercontent.com, writes it to a temporary file, and invokes Bash or PowerShell on it.
AI rationale
The package has no automatic remote execution at install time, but its explicit agent setup executes an unverified remote script. This is a concrete remote-code-execution capability rather than confirmed malware.
Evidence
cli.js
Network endpoints1
raw.githubusercontent.com/kernoio/kerno-agent-runtimes/
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The install hook runs a local banner script, not the CLI agent installer.
- The agent installer is activated through the explicit kerno init command.
- That command downloads a shell script from GitHub, writes it to a temporary path, and launches it with Bash or PowerShell without an integrity check.
Evidence against
- No automatic remote-script execution was found in postinstall.cjs.
- No credential collection or credential forwarding was identified in the inspected installer path.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
cli.js4.65 MB file, sampled 256 KB
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgcli.jsView file
48* Constructs the CommanderError class
L49: * @param {number} exitCode suggested exit code which could be used with process.exit
L50: * @param {string} code an id string representing the error
...
L128: /**
L129: * @api private
L130: */
...
L941: var EventEmitter5 = __require("events").EventEmitter;
L942: var childProcess = __require("child_process");
L943: var path16 = __require("path");
...
L990: this._outputConfiguration = {
L991: writeOut: (str) => process15.stdout.write(str),
L992: writeErr: (str) => process15.stderr.write(str),
Critical
Findings
2 Critical4 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
HighSame File Env Network Executioncli.js
HighCommand Output Exfiltrationcli.js
HighSemantic Analysis Limitedcli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumOversized Source Filecli.js
MediumOversized Cli Entrypointcli.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Low
Affected versions and remediation
This report applies to @kerno/cli@0.2.1.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.2.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.