T06 · System Persistence
- Location
SKILL.md:281- Finding
Persistent Agent Service Installed with Elevated Privileges
- Content
View full analysis
.jwt (0600) — the daemon refreshes it after # creds + URLs in /home/opc/.kax/resident.env (0600) sudo deploy/install-residents.sh 0xSCADA-QE flaukowski kannaka `Restart=always` brings it back; `KAX_TOKEN_FILE` makes the refresh durable, so ``` ### Technical Analysis The Skill instructs users to install a systemd unit under `/etc/systemd/system/` and execute an installer with `sudo`. The resulting resident process is configured with `Restart=always`, stores reusable KAX tokens and service credentials on disk, and refreshes the agent token to preserve access across process restarts. This exceeds the privileges required for ordinary interactive city operations. Entering the city, looking, moving, and speaking only require authenticated HTTP requests; they do not inherently require a privileged, reboot-persistent operating-system service. The referenced `deploy/kax-resident@.service` and `deploy/install-residents.sh` files are not included in the audited project, which contains only `SKILL.md`. Consequently, the commands, execution identity, sandboxing, filesystem permissions, network access, and other behavior of the installed service cannot be verified from this package. Although the documentation specifies file mode `0600`, that protects only against other local users and does not mitigate compromise of the service process, its execution account, or an unreviewed installer. ### Attack Path 1. A user follows the Skill and obtains KAX and NATS credentials. 2. The user places identity tokens in `/home/opc/.kax/.jwt` and credentials a ...[truncated 1309 chars]- Remediation
View remediation
