Apto Payments

Security checks across malware telemetry and agentic risk

Overview

This appears to be a legitimate Apto Payments integration, but it gives an agent broad authenticated payment-account control without clear confirmation safeguards for changes.

Install only if you intend to connect an Apto Payments account through Membrane. Prefer a test or least-privilege account, review granted scopes, require explicit approval before any POST, PUT, PATCH, DELETE, card, transaction, or funding-source change, and revoke the Membrane connection when finished.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
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
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

Confidence: 82% confidence
Finding: The skill description is broad enough to match generic payment-related requests, which can cause the agent to invoke this capability in contexts involving sensitive financial operations without sufficiently narrow scoping. In a payments integration, over-broad routing increases the chance of unnecessary access to account, card, transaction, or merchant data and can lead to unintended external actions.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The skill documents action execution and raw proxy requests against a payment platform but does not warn that these operations may access, transmit, or modify sensitive financial data over the network. In the context of card programs and transactions, missing user-facing warnings and confirmation guidance can lead to silent reads or writes involving highly sensitive payment information.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal