Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

IMAP Email Reader

v1.0.3

Read and manage email via IMAP (ProtonMail Bridge, Gmail, etc.). Check for new/unread messages, fetch content, search mailboxes, and mark as read/unread. Works with any IMAP server including ProtonMail Bridge.

0· 5k·21 current·24 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The code and SKILL.md implement an IMAP reader (checks, fetches, searches, marks read/unread) which matches the skill name and description. However the registry top-level metadata at the beginning of the report states 'Required env vars: none' while skill.json and SKILL.md require IMAP_HOST, IMAP_PORT, IMAP_USER, and IMAP_PASS. This metadata mismatch is an incoherence that could mislead users about what secrets the skill needs.
Instruction Scope
Runtime instructions and scripts stay within the stated scope: they read a local .env, connect to the configured IMAP server, parse messages, and optionally mark flags. setup.sh probes for ProtonMail Bridge via process list and writes .env in the skill folder — actions consistent with onboarding a local Bridge-based IMAP client. There are no instructions that exfiltrate data to unexpected external endpoints.
Install Mechanism
There is no remote URL download; dependencies are normal npm packages (imap-simple, mailparser, dotenv) installed via npm. package.json and package-lock.json are present. This is a standard, traceable install mechanism (npm registry).
!
Credentials
The skill legitimately requires IMAP credentials (IMAP_USER and IMAP_PASS) and related settings. Those are proportionate to the purpose. Concerns: (1) Top-line registry metadata incorrectly lists no required env vars while skill.json declares sensitive IMAP_PASS — an inconsistency that could hide credential requirements. (2) The setup helper writes credentials to a .env file on disk (expected but sensitive). (3) The skill encourages setting IMAP_REJECT_UNAUTHORIZED=false for ProtonMail Bridge; disabling certificate verification is dangerous for networked servers because it makes MITM attacks easier (the SKILL.md notes this but the risk remains).
Persistence & Privilege
The skill is not force-included (always:false) and does not request system-wide privileges or modify other skills. It reads a local .env and uses network access to an IMAP server, which is appropriate for its function.
What to consider before installing
What to consider before installing: - This skill requires your IMAP credentials (IMAP_USER and IMAP_PASS). The included setup helper will store them in a .env file inside the skill folder — only install/run if you accept storing credentials on disk and have .gitignore configured to keep them out of version control. - The registry summary at the top of this package incorrectly claimed 'no required env vars'; don't trust that — the code and skill.json do require credentials. - The skill suggests setting IMAP_REJECT_UNAUTHORIZED=false for ProtonMail Bridge (self-signed cert). Only use that for a trusted local Bridge instance. Never disable certificate verification for public IMAP servers. - The installation uses npm packages from the public registry (imap-simple, mailparser, dotenv). Review/scan dependencies (npm audit) before installing in sensitive environments. - setup.sh checks for a running ProtonMail Bridge by scanning process lists (ps). This is reasonable for detecting Bridge locally but means the script reads process information on the host. - There is no evidence of hidden network exfiltration in the code. Still: if you run this in an agent that can be invoked autonomously, consider running it in an isolated session or sandbox, and prefer app-specific passwords (Gmail app password) where possible. If you want to proceed: verify the skill.json / SKILL.md expectations match (ensure IMAP_PASS is provided and marked sensitive), run npm install in an isolated environment first, and inspect the .env file handling to ensure it meets your security policies.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d8ymzdqsa0sr79py43g43sn80zyrm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments