Security audit

Himalaya

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Himalaya email CLI reference skill; it can access and change configured mailboxes, but those capabilities are disclosed and fit the purpose.

Install only if you are comfortable letting Himalaya access the email accounts you configure. Prefer pass, a system keyring, or another secret manager over raw passwords in config files, keep config permissions tight, and confirm account, folder, message ID, recipient, and attachments before sending, deleting, moving, or downloading mail.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The configuration examples include `backend.auth.raw = "your-password"` and similar SMTP plaintext password storage in the main setup section, which can normalize insecure credential handling. Users may copy the example verbatim into `~/.config/himalaya/config.toml`, exposing mailbox credentials to local compromise, backups, accidental sharing, or source-control leaks.

Static analysis

No suspicious patterns detected.