Back to skill

Security audit

Notifyer by WhatsAble

Security checks for vulnerabilities and agentic risk

Overview

The skill mostly matches its Notifyer automation purpose, but it controls high-impact WhatsApp workspace actions and includes unsafe deletion and credential-handling paths that need manual review.

Install only for a trusted Notifyer workspace operator. Use a least-privileged Notifyer account where possible, avoid running password commands on shared hosts, treat command output as secret-bearing, and be especially careful with delete-broadcast because an arbitrary numeric ID can trigger irreversible remote deletion through an under-scoped backend endpoint.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (3)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
references/broadcasts-reference.md:294
Finding

Broadcast deletion lacks server-side authentication and ownership validation

Content
View full analysis
No script provided. Documented for completeness. DELETE https://api.insightssystem.com/api:6_ZYypAc/broadcast/:broadcast_id Authorization: Bearer Origin: https://console.notifyer-systems.com **Path parameter:** `broadcast_id` (integer — the `id` field, not `broadcast_identifier`) **Xano function stack:** 1. `/cors_origin_console` 2. Get Record From `broadcast_schedule` 3. **Delete Bulk Records In `user's_recipient_phone_numbers`** (cascade delete of all recipients) 4. Delete Record In `broadcast_schedule` **No `/get_user` call** — authentication relies solely on CORS origin check. **Response:** Empty body (HTTP 200). ``` The corresponding script directly invokes the vulnerable endpoint without first verifying that the requested broadcast belongs to the authenticated workspace: ```js const result = await requestJson(config, { method: "DELETE", path: `/api:6_ZYypAc/broadcast/${id}`, body: { broadcast_id: Number(id) }, }); ``` ### Technical Analysis The documented backend function stack does not resolve the bearer token to a user and does not compare the broadcast's owner or workspace with the caller. It relies solely on the `Origin` header through `/cors_origin_console`. CORS is a browser security control, not an authentication or authorization mechanism. Non-browser clients can freely supply: ```http Origin: https://console.notifyer-systems.com ``` The shared API client automatically supplies that header. Although the script requires `NOTIFYER_API_TOKEN` locally, the documented backend function does not call `/get_user`, so the au ...[truncated 1258 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/get-api-key.js:55
Finding

Developer API key is disclosed through standard output and diagnostic output

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/login.js:48
Finding

Account password is accepted as a command-line argument

Content
View full analysis
/cmdline) * for the duration the process runs. On shared/monitored systems, prefer * passing credentials via a wrapper or environment-level secret injection * rather than bare CLI flags visible to other processes. */ ``` ### Technical Analysis Command-line arguments are not an appropriate transport for passwords. Depending on the operating system and process isolation configuration, command arguments may be available through process listings, `/proc//cmdline`, monitoring agents, job-runner metadata, audit systems, and execution telemetry. The Skill's documented login interface requires `--password`, and the implementation provides no hidden interactive prompt, stdin mode, file-descriptor input, or secret-manager integration. Merely documenting the weakness does not mitigate it. ### Attack Path 1. A user invokes the login com ...[truncated 1182 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (392)

Ae3

High
Category
analysis-evasion
Confidence
90% confidence
Finding

Text artifact contains embedded NUL bytes

Content

No source excerpt is available for this finding.

Ae3

High
Category
analysis-evasion
Confidence
90% confidence
Finding

Text artifact contains embedded NUL bytes

Content

No source excerpt is available for this finding.

Ae3

High
Category
analysis-evasion
Confidence
90% confidence
Finding

Text artifact contains embedded NUL bytes

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear description-to-code mismatch. The declared purpose promises substantial Notifyer/WhatsApp account automation features, but the supplied code chunk does not implement any of those capabilities. Instead, it appears to be tar/archive metadata rather than executable logic. Because the actual chunk shows no functional behavior related to WhatsApp templates, bots, campaigns, analytics, logs, or webhooks, the description is not accurately represented by the supplied code.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear mismatch because the declared description promises extensive WhatsApp/Notifyer automation functionality, but the provided code chunk contains only tar/PaxHeader metadata and no actual executable code implementing those features. Since the actual behavior observable from this chunk is merely archive metadata, it does not accurately represent the declared purpose.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear mismatch because the declared description promises substantial Notifyer/WhatsApp automation capabilities, but the provided code chunk only shows tar/PaxHeader metadata and file attributes, not code implementing those features. This is not merely incomplete supporting detail; the actual supplied content has a materially different nature and does not evidence the declared purpose at all.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises a broad set of Notifyer/WhatsApp account automation features. However, the provided code chunk contains only tar/PaxHeader metadata entries and no executable JavaScript implementing any of those functions. Because the actual supplied content does not demonstrate the declared purpose and instead appears to be packaging metadata for a file, this is a material description-to-behavior mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsApp automation capabilities. However, the provided code chunk contains only PaxHeader/tar metadata entries and no executable JavaScript implementing any of those functions. Because the actual supplied content does not demonstrate the declared purpose and instead appears to be packaging metadata, this is a material mismatch between description and observable behavior.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsAble automation capabilities. However, the provided chunk contains only PaxHeader/tar metadata lines and no JavaScript logic. Because there is no executable code demonstrating the declared functionality, the supplied code does not accurately represent the described skill behavior. This is a material mismatch between declared purpose and actual supplied content.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The declared description promises a broad set of Notifyer/WhatsApp automation capabilities. However, the provided code chunk contains only tar/PaxHeader metadata and filesystem provenance attributes, not executable code implementing any of those features. Because the actual supplied content does not reflect the declared primary purpose or capabilities, this is a clear mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises a broad set of Notifyer/WhatsApp automation features. However, the provided code chunk contains only archive header metadata (PaxHeader) and no executable logic demonstrating any of the declared behavior. Because there is no evidence that the code actually performs the stated functions, the supplied code does not accurately represent the declared purpose.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsApp management functionality. However, the provided code chunk is only PaxHeader/archive metadata and contains no executable JavaScript behavior to assess against those claims. Because the actual supplied content does not implement the declared purpose and instead represents file metadata, this is a material description-behavior mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear mismatch because the declared description promises substantial Notifyer/WhatsApp automation capabilities, but the provided code chunk contains only tar/PaxHeader metadata and no actual executable logic demonstrating those functions. Since no relevant behavior is present, the supplied code does not accurately represent the declared purpose.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises a broad set of Notifyer/WhatsApp automation capabilities. However, the provided code chunk is not executable logic implementing those features; it appears to be tar/archive metadata (PaxHeader) for a file, not the file contents themselves. Because the actual supplied code does not demonstrate the declared functionality and instead contains only unrelated archive metadata, the description does not accurately represent the supplied code chunk.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises a broad set of Notifyer/WhatsApp automation functions. However, the provided code chunk contains only tar/PaxHeader metadata entries and no executable code implementing any of those behaviors. Because the actual supplied content does not demonstrate the declared primary purpose or capabilities, this is a clear description-to-behavior mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsApp management functionality, but the provided code chunk contains only archive header metadata and no executable behavior implementing those features. Because the actual supplied content does not demonstrate the declared purpose or any related functionality, the description does not accurately represent the code shown.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear description-behavior mismatch because the provided code does not implement any of the declared Notifyer/WhatsApp management functionality. Instead, it appears to be tar/archive metadata rather than executable logic. With no observable code for template management, bot configuration, broadcasts, analytics, or webhook handling, the supplied chunk materially fails to represent the declared purpose.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear description-to-code mismatch. The declared purpose describes a broad Notifyer/WhatsApp automation skill, but the provided code chunk contains only tar/PaxHeader metadata entries and no executable logic demonstrating any of those capabilities. Because the actual supplied content does not implement the stated functionality and appears unrelated archive metadata rather than operational code, the description is not accurately represented by this code chunk.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear description-behavior mismatch. The declared purpose describes a fully featured Notifyer/WhatsApp automation skill, but the provided code chunk contains only tar/PaxHeader metadata and no functional JavaScript implementing any of those behaviors. Because the supplied code does not evidence the declared capabilities and instead appears unrelated packaging metadata, the description is not accurately represented by the code chunk.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsApp automation capabilities. However, the provided code chunk only shows PaxHeader/tar metadata entries (mtime and xattr provenance fields) for a JavaScript file path and contains no executable logic demonstrating any of the claimed features. Because the actual supplied content does not implement or evidence the declared purpose, this is a clear description-behavior mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial Notifyer/WhatsApp automation capabilities, but the provided code chunk contains only tar/PaxHeader-style metadata and no executable logic demonstrating any of those behaviors. Because the actual supplied content does not implement or evidence the declared functionality, the description does not accurately represent the code chunk.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description promises substantial WhatsApp/Notifyer management capabilities, but the provided code chunk does not implement any of them. Instead, it contains archive header metadata rather than executable logic. This is a material description-behavior mismatch because the actual content shown has no observable automation functionality, API access, webhook handling, analytics retrieval, or bot/template/campaign management.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

Yes, this is a mismatch. The description claims substantial Notifyer/WhatsApp management capabilities, but the provided code chunk contains only tar/PaxHeader metadata and no executable logic implementing those behaviors. Because the actual supplied content is non-functional metadata unrelated to the declared purpose, the description is not accurately represented by this code chunk.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

There is a clear description-to-code mismatch. The declared purpose describes a substantial WhatsApp automation and management skill with API-driven capabilities, but the provided code contains only tar/archive metadata and no executable logic implementing any of those functions. Because no relevant behavior for template management, bot configuration, campaigns, analytics, logs, or webhooks is present, the supplied code does not substantiate the declared functionality.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

There is a clear mismatch because the declared description promises a broad set of Notifyer/WhatsApp automation features, but the provided code chunk contains only tar/PaxHeader metadata lines and no functional code demonstrating any of those behaviors. Since no declared capability is actually implemented or evidenced in the supplied chunk, the description does not accurately represent the actual code content.

Content

No source excerpt is available for this finding.