基于163邮箱SMTP发送邮件功能

WarnAudited by ClawScan on May 10, 2026.

Overview

The skill matches its stated purpose of sending 163 email, but it disables TLS certificate verification while using your email authorization code.

Review or fix the TLS configuration before installing. If you still use it, use a 163 authorization code with minimal intended scope, confirm every recipient and message before sending, and be aware that message details are stored in local log files by default.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

High

#ASI03: Identity and Privilege Abuse

What this means

A network attacker who can intercept the connection could impersonate the SMTP server and capture the email authorization code or message content.

Why it was flagged

The tool reads the 163 SMTP authorization code from the environment and then authenticates over a TLS connection that explicitly skips certificate verification.

Skill content

emailPassword := os.Getenv("EMAIL163_PASSWORD") ... tlsConfig := &tls.Config{ InsecureSkipVerify: true, ServerName: smtpHost }

Recommendation

Do not use this with a real authorization code until TLS verification is fixed; remove InsecureSkipVerify or set it to false, rely on normal certificate validation, and rotate any authorization code already used.

Low

#ASI06: Memory and Context Poisoning

What this means

Copies of sent email details may remain on disk and could be read later by other local processes, backups, or users with file access.

Why it was flagged

The default log path is the current directory, and each send appends a local log entry containing recipient, subject, truncated message content, and result.

Skill content

var logPath = flag.String("log", "./", "日志文件保存路径（可选）") ... 邮件内容: %s ... os.OpenFile(logFilePath, os.O_CREATE|os.O_WRONLY|os.O_APPEND, 0644)

Recommendation

Use a protected log directory, avoid sending highly sensitive content through this tool unless logging is acceptable, and consider adding an explicit no-log option or stricter file permissions.

Low

#ASI02: Tool Misuse and Exploitation

What this means

If invoked without clear approval, the agent could create irreversible outgoing email activity from the user's account.

Why it was flagged

The skill supports sending outbound email, including multi-recipient messages, from the user's configured 163 account.

Skill content

email163 --subject "群发邮件" --info "内容" --to user1@example.com,user2@example.com,user3@example.com

Recommendation

Require explicit user confirmation of recipients, subject, and body before sending any email.