Security audit
Security checks for vulnerabilities and agentic risk
This skill does not show exfiltration or persistence, but it reads sensitive local WhatsApp session/contact data and exposes identifiers with limited user-facing disclosure.
Review this before installing if the workspace contains real WhatsApp/Baileys state. It appears read-only and local, but it can reveal private contacts, phone numbers, group identifiers, and the local cache path; use it only where that disclosure is acceptable.
The stated purpose is limited to listing, searching, and analyzing WhatsApp conversations, but the detected behavior extends to local session/credential metadata, contacts, and storage-path disclosure. This mismatch is dangerous because it can mislead users into granting or invoking a skill for harmless conversation browsing when it actually surfaces sensitive local authentication and account-related information.
The skill exposes code-execution capability via exec(...) but does not declare any tool scope such as permissions or allowed-tools. That makes the privilege boundary unclear and can allow a skill that touches local environment-backed WhatsApp data to run with broader access than users or reviewers expect.
The skill description and usage guidance do not warn that it accesses local WhatsApp data, which is highly sensitive and may include private conversations, contacts, and related account artifacts. In this context, missing disclosure increases the chance of uninformed use and accidental privacy violations because the skill operates against a local Baileys session cache rather than a clearly sandboxed dataset.
The skill description promises listing, searching, and analyzing WhatsApp conversations, but the implementation only inspects local credential/session artifacts and contact metadata. This mismatch is security-relevant because it can mislead users into granting or invoking access to sensitive local WhatsApp state under a broader, inaccurate feature claim, obscuring what data is actually being harvested.
The script reads local WhatsApp session-derived files and contacts.json to enumerate contact IDs, phone numbers, names, and group identifiers, then prints them without any privacy notice, consent flow, or minimization. In this skill context, that is more dangerous because users may expect conversation tooling, not silent extraction of sensitive social-graph metadata from local app state.
The stats output reveals the exact local WhatsApp credential/state directory path, which is unnecessary for normal chat listing or statistics. Exposing internal filesystem paths leaks environment details that can aid follow-on attacks, targeted file access attempts, or user de-anonymization on shared/logged systems.
No suspicious patterns detected.
