registry / @aitherium/awsh / 1.19.0
@aitherium/awsh@1.19.0
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 flagged credential flow is tied to an authorized device login and sends its token to the configured Genesis endpoint for mesh registration. Other reviewed network and shell behaviors support the CLI’s backend, local daemon, and prompted crash-report features; no malicious behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Chat or explicit device login; crash reporting prompts before submission.
Impact
No unauthorized credential redirection, data collection, or account action was established.
Mechanism
Uses the configured backend for requests and registers the endpoint after authorized login. Backend startup can launch the related local agent daemon.
AI rationale
The flagged credential flow is tied to an authorized device login and sends its token to the configured Genesis endpoint for mesh registration. Other reviewed network and shell behaviors support the CLI’s backend, local daemon, and prompted crash-report features; no malicious behavior was found.
Evidence
~/.aither/auth.json
Network endpoints2
gateway.aitherium.comlocalhost:8001
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the CLI through dist/main.js and declares no lifecycle scripts.
- The credentialed mesh registration runs after device login returns an authorized access token.
- Mesh registration uses the configured Genesis URL and sends the token to its /v1/mesh/join endpoint.
- The public gateway default is selected by the explicit --gateway option.
- Crash reports prompt before submission.
Evidence against
- Backend resolution may start an existing local Aitherium agent daemon automatically when it is unavailable.
- The CLI can execute shell commands for user-invoked features such as installation and setup.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.0.
See all versions of @aitherium/awsh for other recorded verdicts.
- Review the evidence and your use of @aitherium/awsh@1.19.0 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.