Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - Read `references/windows-remote.md` when a remote T3 backend runs on Windows.
Security audit
Security checks for vulnerabilities and agentic risk
This setup guide needs review because its unattended server examples can run newly published software without a separate update decision.
Before enabling a background server, choose a specific reviewed T3 release and configure the service to run that installed executable. Approve updates separately, retain a working version for rollback, and confirm who can access each remote server. The remaining persistence and privilege warnings are explained by the disclosed setup workflow.
Referenced artifact was not completely inspected
- Read `references/windows-remote.md` when a remote T3 backend runs on Windows.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
If the result is Linger=no and the service must survive logout, get explicit operator approval before running:
sudo loginctl enable-linger "$USER"
loginctl show-user "$USER" -p Linger
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
systemctl --user daemon-reload
systemctl --user enable --now t3-code.service
systemctl --user status t3-code.service --no-pager
ss -ltn 'sport = :3773'
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
systemctl --user daemon-reload
systemctl --user enable --now t3-code-tunnel-remote.service
systemctl --user status t3-code-tunnel-remote.service --no-pager
journalctl --user -u t3-code-tunnel-remote.service -n 100 --no-pager
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.
git -C /path/to/repository check-ignore -q .idea/icon.svg
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
chmod +x "$HOME/.local/bin/t3-code-serve"
systemctl --user daemon-reload
systemctl --user enable --now t3-code.service
systemctl --user status t3-code.service --no-pager
journalctl --user -u t3-code.service -n 100 --no-pager
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The unattended server command combines automatic installation approval with the mutable latest tag. If retained as a service launch command, subsequent starts can resolve and execute a different release without a separate approval step, potentially introducing compromised code or incompatible changes; loopback binding does not mitigate local package execution.
The unattended headless command automatically approves execution of a package selected through the mutable nightly tag. User acceptance of development-channel risk and a rollback plan reduce surprise but do not prevent later service starts from executing a newly published, unreviewed build.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
systemctl --user daemon-reload
systemctl --user enable --now t3-update.timer
systemctl --user list-timers --all | grep t3
journalctl --user -u t3-update.service -n 100 --no-pager