@aitherium/awsh@1.19.7
awsh - your terminal answers you. Type a question where a command would go, and get an answer instead of "command not found".
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe TUI crash handler silently submits identifying crash diagnostics, creating an undisclosed runtime telemetry path. This is suspicious rather than malicious because the report is limited to crash handling and goes to the configured Genesis service.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An unhandled rejection occurs while the TUI is active; the crash reporter is installed when the CLI starts.
Impact
Hostname and crash diagnostics may leave the machine without the user's consent.
Mechanism
The TUI-specific handler builds a crash report and posts it to the Genesis feedback endpoint without calling the usual confirmation or offline checks.
AI rationale
The TUI crash handler silently submits identifying crash diagnostics, creating an undisclosed runtime telemetry path. This is suspicious rather than malicious because the report is limited to crash handling and goes to the configured Genesis service.
Evidence
dist/main.jsdist/crash-reporter.jsdist/tui/repl-tui.js
Network endpoints1
AITHER_GENESIS_URL (default http://localhost:8001)/feedback
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When an unhandled rejection occurs while the TUI is active, the crash handler submits a report directly instead of using the normal confirmation prompt.
- Crash reports include the machine hostname and system details.
- The CLI installs the crash reporter at startup, and the TUI activates its special crash handling path.
Evidence against
- The package has no install, preinstall, or postinstall hook.
- The ordinary crash-report path asks before submitting; the silent path is limited to unhandled rejections while the TUI is active.
- The wallet command sends its saved token to the Aitherium gateway when the user runs that command.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
12 flaggeddist/repl.jsView file
14import * as readline from 'node:readline';
L15: import { execSync } from 'node:child_process';
L16: import { existsSync, readFileSync, appendFileSync, mkdirSync } from 'node:fs';
High
702else if (!shellCmd) {
L703: console.log(chalk.yellow(' Usage: !command (run in PowerShell 7)'));
L704: console.log(chalk.dim(' !! repeats last shell command'));
High
808patternName = generic_password
severity = medium
line = 808
Medium
dist/crash-reporter.jsView file
Findings
1 Critical10 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/backend-resolver.js
HighChild Processdist/repl.js
HighShelldist/repl.js
HighSame File Env Network Executiondist/crash-reporter.js
HighCredential Exfiltrationdist/wallet-command.js
HighCredential Redirect Persistencedist/commands.js
HighCommand Output Exfiltrationdist/commands.js
HighSandbox Evasion Gated Capabilitydist/rc-command.js
HighTrigger Reachable Credential Exfiltrationdist/wallet-command.js
HighRuntime Package Installdist/backend-command.js#virtual:normalized:round1
HighSemantic Analysis Limiteddist/awconnect-command.js#virtual:normalized:round1
Affected versions and remediation
This report applies to @aitherium/awsh@1.19.7.
See all versions of @aitherium/awsh for other recorded verdicts.
- Review the evidence and your use of @aitherium/awsh@1.19.7 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.