ClawHub
Back to skill

Security audit

antom-integration

Security checks for vulnerabilities and agentic risk

Overview

This skill is a payment-integration helper that relies on online Antom documentation, with no evidence of hidden execution, persistence, credential theft, or destructive behavior.

Before using generated code in production, verify SDK packages, endpoints, signature verification, notification handling, and credential storage against official Antom documentation and review any code examples pulled from remote documents.

A.I.G

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:9
Finding

Mutable Remote Documentation Can Influence Generated Payment Integration Code

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 9–31
Vulnerability Type: Unverified mutable remote dependency
Risk Level: Medium

Evidence

markdown
**All Antom product documentation is available via online dynamic links. Before integration, make sure to read the corresponding product's online documentation to get the latest API parameters and code examples.**

# Document Access Guidelines

To access Antom online documentation, fetch content directly using curl:

```bash
# Example: Get One-time Payments CKP documentation
curl -sL "https://****/****.md"

Important: Before writing code, make sure to read the corresponding product's online documentation via curl. The documentation contains the latest API parameters, code examples, and important notes.

Get Integration Documentation

SDK Selection

  • SDK Selection: To help developers call open interfaces, Alipay provides open platform server-side SDKs, including Java, PHP, Node.js, Python and .NET languages, encapsulating signature and verification, HTTP interface requests and other basic functions. Please download the latest version of the server-side SDK for your language and import it into your development project. SDK Description

Product Selection

Read Product Decision, match keywords based on user input, and only recommend payment products and integration solutions. Always use Clarification Template for product and integration solution confirmation.

> ⛔ Blocking Checkpoint: Product Categories step completion criteria (all of the following must be satisfied before proceeding to subsequent steps)

  • SDK Selection has been read
  • Product documentation ...[truncated 3170 chars]
Remediation
View remediation

Remediation Suggestions

  1. Bundle security-critical integration documentation with the skill after review, or reference immutable, versioned documents hosted on an authenticated official Antom domain.
  2. Pin each remote document to a specific version and verify a published cryptographic digest or digital signature before using its content.
  3. Maintain an explicit allowlist of approved HTTPS hosts and reject redirects to destinations outside that allowlist. Avoid unrestricted curl -L behavior.
  4. Treat downloaded documents as untrusted reference data rather than executable instructions. Explicitly prohibit remote content from changing system instructions, tool policy, security constraints, or permitted domains.
  5. Do not copy or execute commands and code examples from remote documents automatically. Require human review before incorporating them into generated payment code.
  6. Pin SDK package names, registries, publishers, and versions. Verify package signatures or checksums where supported.
  7. Cross-check endpoint addresses, signature rules, notification verification, and credential handling against immutable official documentation before production deployment.
  8. Add content monitoring so unexpected document changes, redirects, domain changes, or integrity verification failures block generation rather than silently accepting new content.

SkillSpector

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