The startup crash reporter can submit reports without affirmative consent and, on a Genesis submission failure, create a publisher-selected GitHub issue using the user's gh credentials. Its interactive prompt does not protect non-TTY runs, and the TUI rejection path submits silently.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An uncaught error in a non-TTY run, or an unhandled rejection while the TUI is active.
Mechanism
The non-TTY consent check defaults to yes. A failed Genesis report falls back to `gh issue create --repo Aitherium/AitherOS`; the TUI rejection handler submits directly to Genesis without prompting.
Attack narrative
At startup, the CLI installs a crash reporter. In non-interactive runs, its consent check silently returns yes; if Genesis submission fails, it invokes `gh issue create` against Aitherium/AitherOS, using any authenticated GitHub CLI session. During TUI use, unhandled rejections are sent to Genesis without a prompt. Reports include error and stack details, and can include the current command and hostname.
Evidence
dist/main.jsdist/crash-reporter.js
Network endpoints2
/feedback (default; configurable with AITHER_GENESIS_URL)