@kerno/cli@0.1.30
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an explicit, product-aligned agent setup flow rather than confirmed covert malware, but it executes unaudited remote code without an integrity check. The risk warrants a warning rather than a publish block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Run kerno init when the agent needs installation or update.
Impact
A change to the remote installer can execute arbitrary commands with the user's privileges and access to inherited environment variables.
Mechanism
Remote shell-script download followed by local shell execution.
AI rationale
This is an explicit, product-aligned agent setup flow rather than confirmed covert malware, but it executes unaudited remote code without an integrity check. The risk warrants a warning rather than a publish block.
Evidence
cli.js
Network endpoints1
raw.githubusercontent.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The init path downloads a shell script from raw.githubusercontent.com, writes it to a temporary file, and executes it.
- The downloaded script runs with the caller's environment and privileges, including on Windows with PowerShell execution-policy bypass.
- The remote installer is separate from the published package, so its behavior cannot be verified from this snapshot.
Evidence against
- The npm postinstall hook only displays a terminal banner; it does not invoke the remote installer.
- Remote execution is reached through the explicit kerno init workflow, not automatically on package installation.
- The inspected CLI prints MCP configuration rather than writing Claude or Cursor configuration files.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
10 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 Critical5 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli.js
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
Affected versions and remediation
This report applies to @kerno/cli@0.1.30.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.30 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.