barkpush

• Outcome: Pass
• Latest audit: May 28, 2026 at 7:47 AM UTC
• Version:
  1.2.0

Overview

This skill is a disclosed Bark notification sender with expected external delivery, local configuration, and local history storage.

Install only if you are comfortable sending the chosen notification content and Bark device identifiers to your configured Bark server. Keep device keys and ciphertext out of shared repositories, prefer environment variables for secrets, and review all-user or delete commands before running them.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The skill promotes push notifications but does not clearly warn that message bodies, titles, links, images, and recipient/device identifiers are transmitted to an external Bark service. Users may unknowingly send sensitive operational or personal data off-system, which is a real privacy and data-handling risk in a notification skill whose core purpose is exfiltrating content to remote devices.

Missing User Warnings

Medium

• Confidence: 87% confidence
• Finding: The documented delete operation can remove previously pushed messages, but no caution is given about permanence, target verification, or accidental destructive use. In a multi-user notification workflow with history and update/delete support, unclear destructive semantics increase the chance of unauthorized or mistaken removal of important alerts or audit-relevant messages.

Missing User Warnings

Medium

• Confidence: 86% confidence
• Finding: The architecture explicitly supports batch and multi-user push operations but does not require an explicit confirmation or warning before sending to multiple recipients. In a notification tool, this increases the risk of accidental mass messaging, unintended disclosure of sensitive content, and operational spam across configured users.

Missing User Warnings

High

• Confidence: 94% confidence
• Finding: The documented all-user mode allows sending content to every configured user without any described safety interlock. In this skill's context, that can amplify mistakes or abuse into organization-wide notification spam and broad unintended distribution of confidential or harmful content.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The sample configuration shows a real credential shape for per-user device keys and includes a ciphertext field, but provides no warning that these are sensitive secrets. This can lead users to hardcode, commit, or share notification credentials, enabling unauthorized pushes, privacy exposure, or misuse of the notification infrastructure.

VirusTotal

65/65 vendors flagged this skill as clean.