โ† Back to Scanner

moonpay Security Audit Report

๐Ÿ”ญ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

moonpay is an AI agent skill, created by 0xterrybit and published at openclaw/skills. ClawSecure audited moonpay across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Warning). The 4 findings concentrate in Hardcoded Secrets, Policy Violation and Permissions Manifest, including Detects potential exposure of sensitive information like API keys,... and Detects potential exposure of sensitive information like API keys,.... 2 were rated high or critical severity.

Is moonpay safe?

ClawSecure audited moonpay and assigned a security score of 55/100 (Warning), identifying 4 findings across Hardcoded Secrets and Policy Violation. Review the findings below before installing.

What did ClawSecure find in moonpay?

ClawSecure identified 4 findings in moonpay, concentrated in Hardcoded Secrets, Policy Violation and Permissions Manifest. 2 were rated high or critical severity. The most severe include Detects potential exposure of sensitive information like API keys,... and Detects potential exposure of sensitive information like API keys,....

How was moonpay audited?

ClawSecure ran moonpay through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files from openclaw/skills.

What does a score of 55 mean?

ClawSecure assigned moonpay a security score of 55/100, placing it in the Warning range. This is driven by 4 findings led by Hardcoded Secrets that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for moonpay

ClawSecure detected 4 security findings in moonpay, spanning Hardcoded Secrets, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for moonpay

Resolve policy violations
moonpay trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standardsโ†’Understanding Our 3-Layer Audit Protocolโ†’How to Secure an MCP Server: The 2026 Guideโ†’

Related AI Agent Security Audits

claude-memScore 45/100crewAIScore 65/100antigravity-awesome-skillsScore 65/100ui-ux-pro-max-skillScore 55/100open-webuiScore 45/100

Scanned on February 7, 2026. moonpay is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan