Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
my_send_email
v1.0.1Send an email by specifying the receiver's address, subject, and content.
⭐ 0· 180·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The name/description and runtime code both implement a simple SMTP email-sending helper — that's coherent. Minor mismatch: _meta.json lists 'smtplib' under requires (standard library) and uses an absolute workspace path; otherwise the requested capabilities are what you'd expect for an email sender.
Instruction Scope
SKILL.md simply instructs running send_mail.py with receiver/subject/content. The code then logs into smtp.cloudtrend.com.cn and sends the provided content. While that is within the stated purpose, the script will transmit arbitrary message content to an external SMTP server using a hardcoded account, which is a high-risk action and not declared in the skill metadata.
Install Mechanism
No install spec and no downloads; the skill is instruction-only with a bundled Python script. This minimizes install-time risk (nothing is fetched or installed at runtime).
Credentials
The skill contains a plaintext SMTP password (password = "A5b3C3D6!") and a fixed sender address inside send_mail.py but declares no required environment variables or credentials. Hardcoding production credentials in-code is disproportionate and inconsistent with the metadata; credentials should be provided via environment/config and not embedded in source.
Persistence & Privilege
The skill does not request 'always: true' and does not modify other skills or global config. It is user-invocable only, which limits its autonomous reach.
Scan Findings in Context
[HARD_CODED_CREDENTIAL_IN_SOURCE] unexpected: The repository contains a plaintext SMTP password and sender email in send_mail.py. The pre-scan reported 'None detected', but manual review finds these credentials embedded in the code. Hardcoded credentials are not expected for a well-configured send-email skill.
What to consider before installing
This skill will send emails using a hardcoded corporate SMTP account embedded in the script. That means the skill can send messages as ai_assistant@cloudtrend.com.cn and the password is stored in plaintext inside the skill. Before installing: do not use production credentials in skills; ask the author to remove the hardcoded password and accept SMTP credentials via secure environment variables or a credentials store; ensure the SMTP account is a dedicated, limited-power account and rotate the password immediately if this code has been exposed; prefer a version that does not include organization credentials in-source. If you must use it, run it in a controlled environment and audit/monitor outgoing emails.Like a lobster shell, security has layers — review code before you run it.
latestvk97draz2werskr1fqrwghgh9q182tb42
License
MIT-0
Free to use, modify, and redistribute. No attribution required.