Self zkID verification
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: self-xyz Version: 1.0.0 The skill bundle provides comprehensive documentation and code examples for integrating the Self identity verification protocol. All instructions and code snippets are directly related to this stated purpose, covering frontend, backend, and smart contract integration. There is no evidence of prompt injection attempts against the agent, data exfiltration, malicious execution, persistence mechanisms, or obfuscation. While the `mock passports` setting in `SelfBackendVerifier` could be a vulnerability if misused in production, it is explicitly documented as 'dev only' and a 'critical gotcha', indicating a configuration risk for the integrator rather than malicious intent from the skill itself.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A production app could unintentionally accept test/mock identities if the setting is not changed.
The backend quick-start shows a verifier setting that accepts mock passports; it is labeled development-only, but identity verification would be weakened if copied into production.
true, // true = accept mock passports (dev only)
Set mock/staging acceptance to false for production, use production endpoint types, and add tests or deployment checks that fail when mock passports are enabled.
Unexpected or compromised dependency versions could affect the user's application.
The guide directs users to install external packages; this is expected for the stated integration, but the example does not pin exact versions.
npm install @selfxyz/qrcode @selfxyz/core
Install from official Self sources, pin versions with a lockfile, and review dependency and contract package provenance before production use.
Proofs and any configured disclosures may reach the developer's backend or contract endpoint.
The intended flow sends verification proofs from the Self app to a public endpoint; this is purpose-aligned, but it is a sensitive data boundary.
Endpoint must be publicly accessible — Self app sends proof directly to your endpoint. Use ngrok for local development.
Use HTTPS, verify endpoint ownership, keep frontend/backend disclosure configs matched, minimize retained data, and be cautious when exposing local development servers with ngrok.
Users may otherwise assume that no personal identity attributes can ever be disclosed.
The documentation clearly lists optional personal-data disclosures, which users should read alongside the privacy-preserving/zero-knowledge framing.
name: true, // disclose full name
dateOfBirth: true, // disclose exact DOB
idNumber: true, // disclose passport/ID numberOnly request the minimum disclosures needed for the application and clearly explain to end users which attributes will be shared.