Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md For install steps and the full field reference, see `references/setup.md`.
Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Supervisor config generator with install-time supply-chain cautions, but the reviewed artifact does not show hidden, destructive, or deceptive behavior.
Before installing, review the downloaded script or pin it to a trusted commit because the setup pulls from GitHub `master`. Avoid the sudo install unless you need all users to run it, back up any existing generated config before rerunning, and inspect the app’s `run.sh` before handing the generated config to Supervisor.
Referenced artifact was not completely inspected
For install steps and the full field reference, see `references/setup.md`.
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
users (requires root)
sudo mv supervisor-config-gen /usr/local/bin/
mkdir -p ~/bin
mv supervisor-config-gen ~/bin/
Then make sure $HOME/bin is on $PATH:
echo $PATH | grep -q "$HOME/bin" && echo "already in PATH" || echo "not in PATH yet"
If not in $PATH, add it (bash: ~/.bashrc, zsh: ~/.zshrc):
echo 'export PATH="$HOME/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
run.sh executable — the script hardcodes command=<dir>/run.sh into the generated config without checking it exists. If there's no run.sh, the generated config will reference a missing file and Supervisor will fail to start the program.There are no CLI flags, positional args, or environment variables. The script (supervisor-config-gen, a single bash file, no subcommands) takes
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo mv supervisor-config-gen /usr/local/bin/
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Prerequisites
- Bash shell on the machine running the script.
- The target app directory MUST contain a `run.sh` executable — the script hardcodes `command=<dir>/run.sh` into the generated config without checking it exists. If there's no `run.sh`, the generated config will reference a missing file and Supervisor will fail to start the program.
## Full input reference
No suspicious patterns detected.