Back to skill

Security audit

Reddit Monitoring

Security checks for vulnerabilities and agentic risk

Overview

This skill is a mostly coherent Reddit monitoring helper, but users should understand it sends watch terms to Veezee, may consume credits, and includes optional setup paths that carry normal third-party dependency risk.

Install only if you are comfortable with your monitored keywords, brand terms, subreddit names, and usage metadata being sent to Veezee for polling. Set a clear polling cadence and max_credits before any unattended loop, review where the Veezee key is stored, prefer the MCP path or a pinned/verified SDK version over unpinned npx, and do not enable X/Twitter escalation unless you explicitly want cross-platform monitoring.

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

T08 · Insecure Dependencies

Warning
Location
SKILL.md:14
Finding

Unpinned Third-Party Package Execution via npx

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 14
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Medium

text
The `veezee` CLI (`npx @veezee/sdk init`, then e.g. `veezee reddit search "<query>" --type comments`) uses the same key.

Technical Analysis

The documented npx @veezee/sdk init command does not specify an exact package version, lockfile, or integrity hash. Depending on the local npm and npx configuration, executing this command can retrieve the package version currently resolved by the npm registry and run its executable code with the invoking user's privileges.

This creates a supply-chain risk because the effective code may change after the Skill has been reviewed. A compromised package release, compromised maintainer account, ownership transfer, or malicious package update could introduce arbitrary code into the initialization path. The audit found no evidence that the package is presently malicious; the vulnerability is the unsafe, mutable dependency-execution pattern.

Attack Path

  1. An attacker compromises the @veezee/sdk package, its publishing credentials, its dependency chain, or the registry resolution path.
  2. The attacker publishes or causes resolution to a release containing malicious initialization or lifecycle code.
  3. A user or Agent follows the Skill documentation and runs:
    shell
    npx @veezee/sdk init
    
  4. npx downloads or resolves the affected package without enforcing a reviewed version or expected integrity value.
  5. The malicious package code executes under the account that invoked the command.

Impact Assessment

Successful exploitation could provide arbitrary code execution with the privileges of the invoking user. The accessible scope could include files readable or writable by that account, environment variables, API credentials, SSH or cloud configuration, Agent configuration, and network-acces ...[truncated 345 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the dependency to an exact reviewed version:
    shell
    npx --yes @veezee/sdk@X.Y.Z init
    
  2. Verify the selected release and its transitive dependencies before recommending it.
  3. Prefer installation through a lockfile-backed project using npm ci, with the lockfile committed and reviewed.
  4. Preserve and validate npm integrity metadata. Where feasible, verify the package archive against a separately published trusted checksum or signature.
  5. Document the expected npm registry explicitly and prevent fallback to untrusted registries or dependency-confusion sources.
  6. Review package lifecycle scripts before installation and disable them with --ignore-scripts when they are not required.
  7. Run initialization in a restricted environment with minimal filesystem access, no unrelated secrets in environment variables, and no administrative privileges.
  8. Establish a controlled dependency-update process so newer versions are reviewed before the documented pin is changed.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The manifest description says to use the skill when the user wants "ongoing Reddit monitoring, brand or competitor tracking, or alerts on new mentions across subreddits." Those phrases are fairly broad and there are no exclusion conditions or negative examples to distinguish this skill from more general social monitoring, alerting, or research requests.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill instructs the agent to run a continuous polling loop against a third-party service without requiring explicit user acknowledgement of ongoing network activity, recurring API calls, budget consumption, and transmission of user-supplied monitoring terms. In this context, monitored topics may contain sensitive business interests, brand-crisis terms, or internal watchlists, so silent external transmission and unattended polling create meaningful privacy and cost risks.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
92% confidence
Finding

The skill directs use of external endpoints at api.veezee.io and mcp.veezee.io, which means user-provided queries, subreddit targets, and potentially usage metadata are transmitted to a third party. External transmission is expected for this skill's function, but it becomes a real security/privacy issue because the instructions do not enforce data-minimization, consent, or restrictions on sending sensitive monitoring topics off-platform.

Content

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

md
Every call needs an API key. Minting one is free and human-free: no signup, no card. A call without a key fails with `KEY_REQUIRED` (401) carrying `mint_url`; the fix is the free mint below, never a payment. A fresh `vz_trial_` key runs under a free per-IP daily budget of 200 credits, cached data only, first page only on any cursor sequence. A monitoring loop makes many calls a day, so that budget exhausts quickly; treat the free tier as a way to test the pattern once, not to run the loop. Two equivalent surfaces; pick whichever your environment has:

- MCP: add the server `https://mcp.veezee.io/reddit` (streamable-http; `https://mcp.veezee.io/all` exposes every platform's tools, useful if you are also escalating to X). Hosts that support MCP authorization (Claude Code, claude.ai) open a Veezee sign-in on connect (email code, no password): that is the whole auth step. Other hosts: mint a key with `POST https://api.veezee.io/v1/keys/mint` (empty body; the key is shown once) and put it in the connection's `Authorization: Bearer` header.
- SDK: `import { VeezeeClient } from "@veezee/sdk"`; `const client = new VeezeeClient(); await client.mint();` mints and stores the free key the first time and reuses it on later runs. Reddit methods live on `client.reddit.search/getSubreddit/getSubredditPosts/getUser/getPost/resolveUrl`. The `veezee` CLI (`npx @veezee/sdk init`, then e.g. `veezee reddit search "<query>" --type comments`) uses the same key.

For a real loop, buy credits: when the free budget or a trial cap runs out (`TRIAL_CAP_EXCEEDED`, `INSUFFICIENT_CREDITS`, `BUDGET_EXHAUSTED`), the error carries `upgrade_url` (https://veezee.io/upgrade) and a machine-readable `offer`; hand that link to your human, and purchases credit the same key directly, nothing to reconfigure.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The manifest describes a skill for continuously monitoring Reddit mentions and subreddit activity. The documentation explicitly instructs users to escalate the same monitoring pattern to x_search on X/Twitter, which is a distinct platform-monitoring capability not justified by the stated Reddit-only purpose.

Content

No source excerpt is available for this finding.