@aitherium/awsh@1.19.3
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 4d ago · by lpm-firewall-aiThe package’s normal key setup is user-driven, but the TUI crash handler silently submits identifying diagnostic data on unhandled rejections. This is undisclosed runtime telemetry, so the package warrants a warning rather than a malware block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An unhandled promise rejection while the TUI is active.
Impact
Diagnostic and identifying information may be sent to the configured Genesis service without the user’s approval.
Mechanism
The crash handler builds a report containing error and stack details, current command, hostname, and machine information, then POSTs it to the Genesis feedback endpoint without prompting.
AI rationale
The package’s normal key setup is user-driven, but the TUI crash handler silently submits identifying diagnostic data on unhandled rejections. This is undisclosed runtime telemetry, so the package warrants a warning rather than a malware block.
Evidence
dist/crash-reporter.js
Network endpoints2
localhost:8001/feedback${AITHER_GENESIS_URL}/feedback
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When the TUI is active, an unhandled rejection submits a crash report silently without asking the user.
- Crash reports include the error message, stack, current command, hostname, and machine details.
- The report is POSTed to the configured Genesis feedback endpoint, which defaults to http://localhost:8001/feedback.
- Outside the silent TUI path, the reporter asks before sending, but defaults to yes and treats non-TTY input as consent.
Evidence against
- The manifest has no install lifecycle scripts; the package is a terminal assistant CLI.
- The DeepSeek setup asks the user to enter a key and stores it through the configured backend as part of the requested setup.
- The crash reporter’s default endpoint is local, and its feedback submission is part of the package’s error-reporting feature.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
10 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 Critical8 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 Redirect Persistencedist/commands.js
HighCommand Output Exfiltrationdist/commands.js
HighSandbox Evasion Gated Capabilitydist/commands.js
HighRuntime Package Installdist/backend-command.js#virtual:normalized:round1
HighSemantic Analysis Limiteddist/awconnect-command.js#virtual:normalized:round1
MediumSecret Patterndist/repl.js
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @aitherium/awsh@1.19.3.
See all versions of @aitherium/awsh for other recorded verdicts.
- Review the evidence and your use of @aitherium/awsh@1.19.3 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.