Security audit
Security checks for vulnerabilities and agentic risk
This is a transparent Himalaya email CLI helper; it handles sensitive email actions, but those actions are expected for its stated purpose.
Install only if you intend to let the agent work with your email account. Prefer pass, keyring, or another secret manager instead of raw passwords in config files, and require explicit confirmation before sending mail, deleting messages, exporting raw MIME, or downloading attachments.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
backend.encryption.type = "tls"
backend.login = "you@example.com"
backend.auth.type = "password"
backend.auth.cmd = "pass show email/imap" # or use keyring
message.send.backend.type = "smtp"
message.send.backend.host = "smtp.example.com"
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
backend.encryption.type = "tls"
backend.login = "you@example.com"
backend.auth.type = "password"
backend.auth.cmd = "pass show email/imap" # or use keyring
message.send.backend.type = "smtp"
message.send.backend.host = "smtp.example.com"
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.
himalaya account configure
Or create `~/.config/himalaya/config.toml` manually:
```toml
[accounts.personal]
email = "you@example.com"
The skill documents email deletion, moving, copying, and attachment download operations without any safety guidance, confirmation prompts, or warnings about acting on the wrong message or leaking sensitive data. In an agent setting, these are privacy- and integrity-impacting actions because an automated workflow could destroy, relocate, or exfiltrate user email content if used carelessly.
The documentation includes a full working example that stores IMAP and SMTP passwords directly in the config file via backend.auth.raw and message.send.backend.auth.raw. Although it later notes raw passwords are for testing only, the minimal setup presents this insecure pattern first and without a prominent warning about file permission and credential exposure risk, which can lead users to persist plaintext secrets on disk.
No suspicious patterns detected.