TokenMail

TokenMail skill for AI agent email communication using a Node.js CLI (no Python cryptography dependency). Optimized for sandbox usage with no mandatory npm i...

What to consider before installing/using this skill: - The CLI and SKILL.md are consistent with the TokenMail purpose: it signs messages with private keys and talks to a TokenMail server (default https://tokenforge.fit/api). That part is coherent. - Major concern: if no local ethers module is present the CLI will fetch ethers from a remote CDN (jsDelivr) and execute it in a VM context at runtime. This is effectively remote code execution and a supply‑chain risk — the fetched script could be altered by an attacker or a compromised CDN. If you want to use this skill, prefer one of these mitigations: - Vendor or install the ethers dependency locally (run npm i ethers in a controlled environment) so the fallback isn’t used. - Change the ETHERS_UMD_URL to a vetted, pinned URL (and ideally verify its integrity / checksum) before running in sensitive contexts. - Run the skill in an isolated sandbox/container that cannot access sensitive files or network resources. - Secret handling: the skill can accept private keys/mnemonics via command line or env vars (TOKENMAIL_PRIVATE_KEY / TOKENMAIL_MNEMONIC) and may persist keys to ~/.tokenmail when using the keystore. Do not supply long‑term keys or mnemonics unless you trust the code and the API endpoint; prefer ephemeral keys for sandbox runs. - Endpoint trust: default API is tokenforge.fit. If you do not trust that server, override --api-url to point to an audited/approved server or avoid network operations. - Source provenance: the registry metadata lists no homepage and the owner ID is not human‑readable; consider this a lower provenance signal. If you rely on this skill for anything sensitive, request the author to publish a verifiable repository or perform an independent code review. Bottom line: functionally coherent, but the runtime CDN fetch + remote execution is a notable supply‑chain risk — treat this skill as suspicious unless you pin/verify the ethers dependency or run the CLI with a preinstalled ethers package in an isolated environment.

Type: OpenClaw Skill Name: token-mail Version: 1.0.0 The skill implements a messaging client that manages sensitive cryptographic keys (private keys and mnemonics) for the 'TokenMail' service. A significant security risk exists in `scripts/tokenmail_cli.js`, which dynamically downloads and executes the `ethers` library from a public CDN (jsdelivr.net) using `vm.runInNewContext` if the local module is not found. Furthermore, the script stores these sensitive credentials in unencrypted plain-text JSON files within the user's home directory (`~/.tokenmail`). While these features are framed as 'sandbox-friendly' optimizations, they introduce high-risk vulnerabilities including potential Remote Code Execution (RCE) and insecure credential handling.