Credential Access
- Category
- Privilege Escalation
- Confidence
- 70% confidence
- Finding
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Content
md ends an anonymous heartbeat each time it runs a Gene — a random machine id, the channel and the CLI version, nothing else; `ROTIFER_TELEMETRY=0` or `DO_NOT_TRACK=1` stops it too. Argument values, file contents, environment variables and your local configuration are not sent. | | **Credentials** | It does not read your environment variables or other tools' secrets, and it cannot log you in or out. Public data needs no login. If you log in yourself with `rotifer login`, the session token is saved to `~/.rotifer/credentials.json` with `0600` permissions. The MCP server then attaches it to its Rotifer API requests and usage records, and renews it there when it expires, writing the new token back to the same file. It is not shown to the assistant and is sent nowhere else. Genes and Agents do not live there — they are project files. | **Every replacement is confirmed by you.** `/evolve` and `/evolve status` only read and report. `/evolve upgrade` proposes a specific swap and waits — no Gene
