Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Clevr Pay
v1.0.1Cleanverse / ClevrPay skill for trusted global payments, compliant stablecoin settlement, financial-identity-based payments, Access Pass (A-Pass) eligibility...
⭐ 0· 33·0 current·0 all-time
by@umy997
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to operate through locally-configured API endpoints and says 'No hardcoded external URLs are exposed', but both the SKILL.md API docs and the included script contain explicit sandbox and production base URLs (https://uatapi.cleanverse.com and https://api.cleanverse.com). This is an internal inconsistency that should be explained by the author. Apart from that mismatch, the required actions (querying pass status, deposit addresses, registration) align with the payment purpose.
Instruction Scope
Runtime instructions focus on querying Cleanverse APIs (get_magiclink, query_apass, query_deposit_address, etc.) and guiding the user through an authentication magic-link flow; they do not request private keys or unrelated system files. However the APIs return KYC-related fields (e.g., currentKycHash) per the docs — those are sensitive and the SKILL.md does not explicitly warn users or constrain how that data is handled or displayed.
Install Mechanism
No install steps; the skill is instruction-first with a small Python helper that uses only standard libraries. This is low-risk in terms of arbitrary code downloads or disk persistence.
Credentials
No environment variables or credentials are requested, which is proportionate. However the included API docs contain an RPC URL with an apparent embedded API key (example: https://solana-devnet.g.alchemy.com/v2/_ztkT79iUO-dFpkTNDBFB). That looks like a sensitive token embedded in documentation and is inconsistent with the 'no hardcoded external URLs' statement. Also, the APIs may return KYC hashes and other identity-linked data, so the skill will surface sensitive user verification data even though it asks for no auth — you should confirm what the backend returns and who controls it.
Persistence & Privilege
The skill does not request 'always: true' or other elevated persistence. Model invocation is allowed (platform default). There is no evidence the skill modifies other skills or system settings.
What to consider before installing
Before installing or enabling this skill, do the following:
- Ask the skill owner to explain the contradiction between the SKILL.md's claim of 'locally-configured API endpoints / no hardcoded external URLs' and the fact the docs and helper script contain explicit sandbox and production base URLs (uatapi.cleanverse.com and api.cleanverse.com). Confirm which endpoints your agent will actually call.
- Verify the provenance of any embedded RPC or API keys shown in the docs (the example Alchemy URL contains what looks like a key). If those are real, they must be removed; if they are placeholders, confirm they are placeholders.
- Confirm what sensitive fields the backend returns (e.g., currentKycHash or other identity/KYC data) and decide whether your agent should display or store them. Limit the agent's ability to return or log PII/KYC data unless you intend that.
- Test the workflow in the sandbox environment first (use --env sandbox) and avoid production until you have validated behavior and ownership of the endpoints.
- Do not provide private keys or paste seed phrases into the agent. The skill recommends using an EVM wallet skill for wallet creation — ensure that wallet skill has proper safeguards.
- If you plan to allow autonomous agent invocation that can call this skill, consider restricting or reviewing those capabilities since this skill deals with financial/KYC data and could widen impact.
If the author cannot clearly justify the hardcoded endpoints and the embedded RPC key, treat the package as untrusted and do not use it for production payments.Like a lobster shell, security has layers — review code before you run it.
latestvk975ay6xx0t3zspd7qrhbfqt99842xq8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.