In-App Purchases

• Outcome: Review
• Latest audit: May 28, 2026, 12:55 PM
• Version:
  1.0.0

Overview

The skill is documentation-only and not malicious, but several payment-system examples omit safeguards that users should review before copying into production.

Install only if you want reference material for IAP implementation, and treat its code snippets as sketches rather than production-ready security patterns. Before using them in a real app, require backend-only secret storage, authenticated webhooks, idempotent entitlement updates, careful receipt/token retention, privacy review, and clear paywall disclosures.

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 (6)

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The webhook example persists user-linked revenue events using app_user_id together with product, price, currency, and timestamp, creating a behavioral purchase history tied to an individual identifier. Without any mention of webhook signature verification, minimization, retention limits, or disclosure to users, this pattern can lead to unnecessary exposure of potentially identifiable financial telemetry and increases privacy/compliance risk if the database is accessed or reused improperly.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The guidance promotes 'trial first, price second' framing that can obscure when billing begins and whether a subscription auto-renews. In an in-app purchases skill, this is especially risky because teams may copy this wording directly into production paywalls, increasing the chance of deceptive UX, policy violations, chargebacks, and regulatory scrutiny.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: Recommending vague CTA text like 'Continue' for a purchase flow can mislead users about the financial consequence of tapping, particularly when a paid trial or recurring subscription may begin. In the paywall-design context, this is more dangerous because the document is prescribing conversion tactics, so ambiguous labels are likely to be implemented as dark-pattern purchase UX.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The webhook example grants, extends, and revokes access based solely on `req.body` with no signature verification, shared-secret validation, or source authentication. In a subscription system, an attacker who can send forged requests to this endpoint could trigger entitlement changes and manipulate billing state, leading to unauthorized premium access or denial of service for paying users.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The REST API examples demonstrate sensitive subscriber reads and entitlement modifications using a secret API key, but they provide no warning that this credential must remain server-side and tightly protected. In practice, developers may copy this pattern into client apps, logs, or scripts, exposing a key that allows direct access to subscriber data and promotional entitlement changes.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The guidance explicitly recommends storing raw receipts for dispute resolution, but it does not mention that receipts and purchase tokens are sensitive payment-linked artifacts that may contain personal or account-related data. Retaining them without minimization, encryption, access controls, and defined retention periods increases the risk of privacy exposure, token misuse, and regulatory noncompliance if the database or logs are accessed improperly.

VirusTotal

64/64 vendors flagged this skill as clean.