WhatsApp HappyBDay

Monitor WhatsApp groups to dynamically detect people who should be congratulated. It identifies keywords (e.g., "birthday", "congratulations") and the person...

What to consider before installing: - Metadata mismatch: the skill's declared required env vars omit BIRTHDAY_SKIP_LIST (used by the code) and incorrectly lists BIRTHDAY_MIN_MESSAGES as the primary credential — treat these as errors in the package metadata. - Command-injection risk: the script uses subprocess.run(..., shell=True) and builds shell commands containing group JIDs and generated messages (which can include extracted names from chat text). Untrusted group content could be crafted to inject shell commands. Before enabling the skill (especially with BIRTHDAY_SIMULATE=false), either: (a) review and harden the code to use subprocess.run([...], shell=False) or properly escape/quote inputs, or (b) sandbox execution (container) and keep it in simulation mode. - Simulation first: keep BIRTHDAY_SIMULATE=true and test extensively. Inspect messages.json and scoring_words.json defaults and your skip list to avoid unwanted sends. - Dependency and runtime: ensure python-dotenv is installed in the environment the agent will run in; the script exits if dotenv is missing. The script also contains a hardcoded user-site path fallback which is odd but not critical. - Autonomy and cron: because the skill is intended for periodic autonomous runs, only enable it if you are comfortable with an automated agent sending messages on your behalf. If you need help making the subprocess usage safe, seek a code fix that removes shell=True and uses argument lists, or that sanitizes user-derived strings before embedding them into shell commands.

Type: OpenClaw Skill Name: whatsapp-happybday Version: 1.0.2 The skill automates WhatsApp congratulations using the `wacli` tool, but contains a significant shell injection vulnerability in `scripts/whatsapp_happybday.py`. The script uses `subprocess.run` with `shell=True` to execute commands constructed from external data (such as group JIDs) without sanitization. Additionally, the code includes hardcoded local developer paths and redundant environment checks. While the behavior aligns with the stated purpose and no clear malicious intent or exfiltration was found, the high-risk command execution logic is a critical security flaw.