Didit Id Document Verification

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:13 PM UTC
• Version:
  1.2.0

Overview

This skill does what it says: it sends user-chosen ID document images to Didit for verification, but the documents and returned data are highly sensitive.

Install only if you are authorized to send the document holder's ID images to Didit. Keep DIDIT_API_KEY secret, use --no-save when provider-side saving is not needed, avoid unnecessary vendor_data, and protect the returned JSON because it can include document numbers, birth dates, addresses, portraits, and document images.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The skill describes sending images of passports, IDs, licenses, and extracted personal data to a third-party verification API, but it does not prominently warn the user that extremely sensitive identity data will leave the local environment. Because this is KYC-grade data, users may unknowingly transmit regulated PII and document images without informed consent or awareness of third-party processing.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The documented default of `save_api_request=true` means submitted ID images and verification payloads may be retained in the provider's Business Console, yet this storage behavior is not prominently disclosed. Silent retention of document photos and extracted identity attributes materially increases privacy, compliance, and breach exposure for especially sensitive KYC data.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The script transmits highly sensitive identity-document images and optional vendor/session identifiers to a remote third-party API, but the CLI provides no meaningful user-facing privacy notice, consent prompt, or data-retention warning. In a KYC/document-verification skill, this is especially sensitive because passports, IDs, MRZ data, and related identifiers are high-value personal data subject to privacy, compliance, and breach risks.

VirusTotal

65/65 vendors flagged this skill as clean.