Back to skill

Security audit

Web Push Notifications

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Web Push reference skill, but users should handle push credentials and subscription data carefully.

Install with normal npm supply-chain care, preferably as a pinned local project dependency rather than a global unpinned CLI. Treat VAPID private keys, GCM keys, and push subscription endpoint/key material as sensitive, avoid pasting real secrets into command-line arguments, and disclose and protect backend storage of user push subscriptions.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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 (2)

T08 · Insecure Dependencies

Warning
Location
references/webpush.md:6
Finding

Unpinned Third-Party npm Dependency Installation

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:108
Finding

Sensitive Push Credentials Passed Through Command-Line Arguments

Content
View full analysis
--auth= \ --vapid-subject=mailto:example@qq.com \ --vapid-pubkey= --vapid-pvtkey= \ --payload="Hello" [--ttl=] [--encoding=aesgcm|aes128gcm] ``` `references/webpush.md:135-145`: ```bash web-push send-notification \ --endpoint=https://fcm.googleapis.com/fcm/send/... \ --key= \ --auth= \ --payload="Message content" \ --vapid-subject=mailto:example@qq.com \ --vapid-pubkey= \ --vapid-pvtkey= \ --ttl=3600 \ --encoding=aes128gcm \ --gcm-api-key= ``` ### Technical Analysis The examples direct users to substitute sensitive values directly into command-line arguments. These values include: - The VAPID private key used to authenticate the application server. - The legacy GCM API key. - The subscription authentication secret. - Subscription key material and endpoint information. Command-line arguments may be retained in shell history, terminal recordings, CI/CD logs, diagnostic output, audit systems, or process-monitoring interfaces. On systems where process arguments are visible to other users or monitoring agents, credentials can be collected while the command is running. Copying the command into scripts or support tickets can create additional persistent copies. Payload encryption is necessary for Web Push and the outbound request itself is consistent with the declared functionality. However, exposing credentials through `argv` is not necessary to perform that function and exceeds the minimum safe disclosure surface. ### Attack Path 1. A user replaces ...[truncated 1416 chars]
Remediation
View remediation
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Hidden Instructions

High
Category
Prompt Injection
Confidence
60% confidence
Finding

Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 1)May include surrounding context.

md
# web-push Complete API Reference

## Installation & Configuration

Hidden Instructions

High
Category
Prompt Injection
Confidence
60% confidence
Finding

Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Content

Scanner excerpt · references/webpush.md (reported line 1)May include surrounding context.

md
# web-push Complete API Reference

## Installation & Configuration

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

The client-side example instructs sending subscription.toJSON() to /api/subscribe, which includes endpoint and key material associated with the user's push subscription. In this markdown file, there is no accompanying warning that subscription details are being transmitted to a backend or that they should be handled as user-associated data.

Content

No source excerpt is available for this finding.