Security audit

Whatsapp Private Domain Ops

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed Chinese-language WhatsApp marketing strategy skill with advisory scripts and no evidence of hidden execution, credential use, persistence, or data exfiltration.

Install only if you want Chinese-language WhatsApp operations planning. Treat its marketing and account-health recommendations as advisory, and verify current Meta/WhatsApp rules and applicable privacy or anti-spam laws before using the generated plans or templates with real customers.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The usage section lists generic trigger phrases such as diagnosing an account, generating compliant messaging, and designing operating strategies, but it does not define explicit trigger phrases, scope limits, or exclusion conditions. Because these requests are common across many business and marketing contexts, the activation boundary for this skill is ambiguous.

Natural-Language Policy Violations

Medium

Confidence: 96% confidence
Finding: The entire skill, including headings, instructions, templates, and invocation examples, is written only in Chinese and does not state that users may choose another language. Under the policy, a skill that implicitly requires a specific language without opt-in is a natural-language policy violation unless the locale restriction is clearly justified.

Natural-Language Policy Violations

Medium

Confidence: 90% confidence
Finding: The title is written entirely in Chinese, and the manifest does not state that the skill is region-specific or that users may choose another language. This can violate language/locale policy expectations because it imposes a language preference without opt-in or justification.

Natural-Language Policy Violations

Medium

Confidence: 93% confidence
Finding: The file’s title, feature descriptions, enum values, docstrings, CLI usage, and user-facing output are predominantly in Chinese, while the tool does not provide any user opt-in or option to select another language. Under the policy for natural-language violations, forcing a specific language without user choice is in scope even when it appears in code strings and comments.

Natural-Language Policy Violations

Low

Confidence: 90% confidence
Finding: This markdown file contains a full compliance reference in Chinese, but it does not indicate that Chinese is required, optional, or limited to a specific audience. Under the natural-language policy rule, forcing a specific language without user opt-in can be a locale/language policy issue.

Static analysis

No suspicious patterns detected.